Change prosody.cfg.lua and docker-compose.yaml

docker-compose.yaml

@@ -0,0 +1,18 @@
+services:
+  prosody:
+    image: prosody/prosody:latest
+    container_name: prosody
+    stdin_open: true
+    tty: true
+    environment:
+      __FLUSH_LOG: 1
+    ports:
+      - "5222:5222"
+      - "5269:5269"
+      - "5000:5000"
+      - "5582:5582"
+      - "5583:5583"
+      - "5347:5347"
+    volumes:
+      - ./prosody:/etc/prosody
+    restart: unless-stopped

prosody/prosody.cfg.lua

@@ -1,7 +1,55 @@
-admins = { "q@porno4free.ru" } 
-plugin_paths = {"/etc/prosody/prosody-modules"}
-daemonize = false
+-- Prosody Example Configuration File
+--
+-- If it wasn't already obvious, -- starts a comment, and all
+-- text after it on a line is ignored by Prosody.
+--
+-- The config is split into sections, a global section, and one
+-- for each defined host that we serve. You can add as many host
+-- sections as you like.
+--
+-- Lists are written
+_ = { "like", "this", "one" }
+-- Lists can also be of { 1, 2, 3 } numbers, etc.
+-- Either commas, or semi-colons; may be used
+-- as separators.
+--
+-- A table is a list of values, except each value has a name. An
+-- example would be:
+--
+example_ssl = { key = "keyfile.key", certificate = "certificate.crt" }
+--
+-- Whitespace (that is tabs, spaces, line breaks) is mostly insignificant, so
+-- can
+-- be placed anywhere
+-- that   you deem fitting.
+--
+-- Tip: You can check that the syntax of this file is correct
+-- when you have finished by running this command:
+--     prosodyctl check config
+-- If there are any errors, it will let you know what and where
+-- they are, otherwise it will keep quiet.
+--
+-- The only thing left to do is rename this file to remove the .dist ending, and fill in the
+-- blanks. Good luck, and happy Jabbering!
 
+
+---------- Server-wide settings ----------
+-- Settings in this section apply to the whole server and are the default settings
+-- for any virtual hosts
+
+-- This is a (by default, empty) list of accounts that are admins
+-- for the server. Note that you must create the accounts separately
+-- (see https://prosody.im/doc/creating_accounts for info)
+-- Example: admins = { "user1@example.com", "user2@example.net" }
+admins = { }
+
+-- This option allows you to specify additional locations where Prosody
+-- will search first for modules. For additional modules you can install, see
+-- the community module repository at https://modules.prosody.im/
+--plugin_paths = {}
+
+-- This is the list of modules Prosody will load on startup.
+-- Documentation for bundled modules can be found at: https://prosody.im/doc/modules
 modules_enabled = {
 
     -- Generally required
@@ -18,7 +66,8 @@ modules_enabled = {
         "limits"; -- Enable bandwidth limiting for XMPP connections
         "pep"; -- Allow users to store public and private data in their account
         "private"; -- Legacy account storage mechanism (XEP-0049)
-		"smacks"; -- Stream management and resumption (XEP-0198) "vcard4"; -- User profiles (stored in PEP)
+        "smacks"; -- Stream management and resumption (XEP-0198)
+        "vcard4"; -- User profiles (stored in PEP)
         "vcard_legacy"; -- Conversion between legacy vCard and PEP Avatar, vcard
 
     -- Nice to have
@@ -31,21 +80,21 @@ modules_enabled = {
         "time"; -- Let others know the time here on this server
         "uptime"; -- Report how long server has been running
         "version"; -- Replies to server version requests
-		"mam"; -- Store recent messages to allow multi-device synchronization
-		"turn_external"; -- Provide external STUN/TURN service for e.g. audio/video calls
+        --"mam"; -- Store recent messages to allow multi-device synchronization
+        --"turn_external"; -- Provide external STUN/TURN service for e.g. audio/video calls
+
     -- Admin interfaces
         "admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
         "admin_shell"; -- Allow secure administration via 'prosodyctl shell'
-		"admin_telnet";
+
     -- HTTP modules
         --"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
-		"http_openmetrics"; -- for exposing metrics to stats collectors
+        --"http_openmetrics"; -- for exposing metrics to stats collectors
         --"websocket"; -- XMPP over WebSockets
-		"unknown"
 
     -- Other specific functionality
         --"announce"; -- Send announcement to all online users
-		-- "groups"; -- Shared roster support
+        --"groups"; -- Shared roster support
         --"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
         --"mimicking"; -- Prevent address spoofing
         --"motd"; -- Send a message to users when they log in
@@ -57,67 +106,165 @@ modules_enabled = {
         --"welcome"; -- Welcome users who register accounts
 }
 
+-- These modules are auto-loaded, but should you want
+-- to disable them then uncomment them here:
 modules_disabled = {
     -- "offline"; -- Store offline messages
     -- "c2s"; -- Handle client connections
     -- "s2s"; -- Handle server-to-server connections
     -- "posix"; -- POSIX functionality, sends server to background, etc.
 }
--- Auth -- 
-allow_unencrypted_plain_auth = true
-c2s_require_encryption = false
+
+
+-- Server-to-server authentication
+-- Require valid certificates for server-to-server connections?
+-- If false, other methods such as dialback (DNS) may be used instead.
+
 s2s_secure_auth = true
-allow_registration = false
-registration_invite_only = false 
-authentication = "internal_hashed"
-   cyrus_service_name = "xmpp"
+
+-- Some servers have invalid or self-signed certificates. You can list
+-- remote domains here that will not be required to authenticate using
+-- certificates. They will be authenticated using other methods instead,
+-- even when s2s_secure_auth is enabled.
+
+--s2s_insecure_domains = { "insecure.example" }
+
+-- Even if you disable s2s_secure_auth, you can still require valid
+-- certificates for some domains by specifying a list here.
+
+--s2s_secure_domains = { "jabber.org" }
+
+
+-- Rate limits
+-- Enable rate limits for incoming client and server connections. These help
+-- protect from excessive resource consumption and denial-of-service attacks.
 
 limits = {
     c2s = {
-		rate = "1000kb/s";
+        rate = "10kb/s";
     };
     s2sin = {
-		rate = "3000kb/s";
+        rate = "30kb/s";
     };
 }
 
-pidfile = "/run/prosody/prosody.pid"
+-- Authentication
+-- Select the authentication backend to use. The 'internal' providers
+-- use Prosody's configured data storage to store the authentication data.
+-- For more information see https://prosody.im/doc/authentication
+
+authentication = "internal_hashed"
+
+-- Many authentication providers, including the default one, allow you to
+-- create user accounts via Prosody's admin interfaces. For details, see the
+-- documentation at https://prosody.im/doc/creating_accounts
+
+
+-- Storage
+-- Select the storage backend to use. By default Prosody uses flat files
+-- in its configured data directory, but it also supports more backends
+-- through modules. An "sql" backend is included by default, but requires
+-- additional dependencies. See https://prosody.im/doc/storage for more info.
 
--- Arhive Message --
 --storage = "sql" -- Default is "internal"
---sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "okArkhipsql)(%", host = "localhost" }
 
-archive_expires_after = "never"
+-- For the "sql" backend, you can uncomment *one* of the below to configure:
+--sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
+--sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
+--sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
 
--- TURN --
-turn_external_host = "bebrik.xyz"
-turn_external_secret = "jasdkfladkjfadsklfagj12"
 
+-- Archiving configuration
+-- If mod_mam is enabled, Prosody will store a copy of every message. This
+-- is used to synchronize conversations between multiple clients, even if
+-- they are offline. This setting controls how long Prosody will keep
+-- messages in the archive before removing them.
+
+archive_expires_after = "1w" -- Remove archived messages after 1 week
+
+-- You can also configure messages to be stored in-memory only. For more
+-- archiving options, see https://prosody.im/doc/modules/mod_mam
+
+
+-- Audio/video call relay (STUN/TURN)
+-- To ensure clients connected to the server can establish connections for
+-- low-latency media streaming (such as audio and video calls), it is
+-- recommended to run a STUN/TURN server for clients to use. If you do this,
+-- specify the details here so clients can discover it.
+-- Find more information at https://prosody.im/doc/turn
+
+-- Specify the address of the TURN service (you may use the same domain as XMPP)
+--turn_external_host = "turn.example.com"
+
+-- This secret must be set to the same value in both Prosody and the TURN server
+--turn_external_secret = "your-secret-turn-access-token"
+
+
+-- Logging configuration
 -- For advanced logging see https://prosody.im/doc/logging
 log = {
-	info = "/var/log/prosody/prosody.log"; -- Change 'info' to 'debug' for verbose logging
-	error = "/var/log/prosody/prosody.err";
-	debug = "/var/log/prosody/prosody_debug.log";
+    info = "prosody.log"; -- Change 'info' to 'debug' for verbose logging
+    error = "prosody.err";
+    -- "*syslog"; -- Uncomment this for logging to syslog
+    -- "*console"; -- Log to the console, useful for debugging when running in the foreground
 }
+
+
+-- Uncomment to enable statistics
+-- For more info see https://prosody.im/doc/statistics
+-- statistics = "internal"
+
+
+-- Certificates
+-- Every virtual host and component needs a certificate so that clients and
+-- servers can securely verify its identity. Prosody will automatically load
+-- certificates/keys from the directory specified here.
+-- For more information, including how to use 'prosodyctl' to auto-import certificates
+-- (from e.g. Let's Encrypt) see https://prosody.im/doc/certificates
+
+-- Location of directory to find certificates in (relative to main config file):
 certificates = "certs"
 
 ----------- Virtual hosts -----------
-VirtualHost "porno4free.ru"
-ssl = {
-	key = "/etc/prosody/ssl/porno4free.ru.key";
-	certificate = "/etc/prosody/ssl/porno4free.ru.fullchain.pem";
-}
+-- You need to add a VirtualHost entry for each domain you wish Prosody to serve.
+-- Settings under each VirtualHost entry apply *only* to that host.
+
+VirtualHost "localhost"
+-- Prosody requires at least one enabled VirtualHost to function. You can
+-- safely remove or disable 'localhost' once you have added another.
+
+
+--VirtualHost "example.com"
 
 ------ Components ------
-Component "chat.porno4free.ru" "muc"
-    modules_enabled = { "muc_mam" }
-    restrict_room_creation = "local" 
-    muc_room_default_language = "ru"
-    muc_room_default_history_length = 228
+-- You can specify components to add hosts that provide special services,
+-- like multi-user conferences, and transports.
+-- For more information on components, see https://prosody.im/doc/components
 
-Component "proxy.porno4free.ru" "proxy65"
+---Set up a MUC (multi-user chat) room server on conference.example.com:
+--Component "conference.example.com" "muc"
+--- Store MUC messages in an archive and allow users to access it
+--modules_enabled = { "muc_mam" }
 
-Component "uploads.porno4free.ru" "http_upload_external"
-	http_upload_external_base_url = "https://uploads.porno4free.ru/"
-	http_upload_external_secret = "bebra228"
-	http_upload_external_file_size_limit = 2147483648
+---Set up a file sharing component
+--Component "share.example.com" "http_file_share"
+
+---Set up an external component (default component port is 5347)
+--
+-- External components allow adding various services, such as gateways/
+-- bridges to non-XMPP networks and services. For more info
+-- see: https://prosody.im/doc/components#adding_an_external_component
+--
+--Component "gateway.example.com"
+--  component_secret = "password"
+
+
+---------- End of the Prosody Configuration file ----------
+-- You usually **DO NOT** want to add settings here at the end, as they would
+-- only apply to the last defined VirtualHost or Component.
+--
+-- Settings for the global section should go higher up, before the first
+-- VirtualHost or Component line, while settings intended for specific hosts
+-- should go under the corresponding VirtualHost or Component line.
+--
+-- For more information see https://prosody.im/doc/configure