IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an email to s dot adaszewski at gmail dot com. User accounts are meant only to report issues and/or generate pull requests. This is a purpose-specific Git hosting for ADARED projects. Thank you for your understanding!
Du kan inte välja fler än 25 ämnen Ämnen måste starta med en bokstav eller siffra, kan innehålla bindestreck ('-') och vara max 35 tecken långa.

209 lines
8.6KB

  1. -- Prosody Example Configuration File
  2. --
  3. -- Information on configuring Prosody can be found on our
  4. -- website at https://prosody.im/doc/configure
  5. --
  6. -- Tip: You can check that the syntax of this file is correct
  7. -- when you have finished by running this command:
  8. -- prosodyctl check config
  9. -- If there are any errors, it will let you know what and where
  10. -- they are, otherwise it will keep quiet.
  11. --
  12. -- The only thing left to do is rename this file to remove the .dist ending, and fill in the
  13. -- blanks. Good luck, and happy Jabbering!
  14. ---------- Server-wide settings ----------
  15. -- Settings in this section apply to the whole server and are the default settings
  16. -- for any virtual hosts
  17. -- This is a (by default, empty) list of accounts that are admins
  18. -- for the server. Note that you must create the accounts separately
  19. -- (see https://prosody.im/doc/creating_accounts for info)
  20. -- Example: admins = { "user1@example.com", "user2@example.net" }
  21. admins = { }
  22. -- Enable use of libevent for better performance under high load
  23. -- For more information see: https://prosody.im/doc/libevent
  24. --use_libevent = true
  25. -- Prosody will always look in its source directory for modules, but
  26. -- this option allows you to specify additional locations where Prosody
  27. -- will look for modules first. For community modules, see https://modules.prosody.im/
  28. --plugin_paths = {}
  29. -- This is the list of modules Prosody will load on startup.
  30. -- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
  31. -- Documentation for bundled modules can be found at: https://prosody.im/doc/modules
  32. modules_enabled = {
  33. -- Generally required
  34. "roster"; -- Allow users to have a roster. Recommended ;)
  35. "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
  36. "tls"; -- Add support for secure TLS on c2s/s2s connections
  37. "dialback"; -- s2s dialback support
  38. "disco"; -- Service discovery
  39. -- Not essential, but recommended
  40. "carbons"; -- Keep multiple clients in sync
  41. "pep"; -- Enables users to publish their avatar, mood, activity, playing music and more
  42. "private"; -- Private XML storage (for room bookmarks, etc.)
  43. "blocklist"; -- Allow users to block communications with other users
  44. "vcard4"; -- User profiles (stored in PEP)
  45. "vcard_legacy"; -- Conversion between legacy vCard and PEP Avatar, vcard
  46. -- Nice to have
  47. "version"; -- Replies to server version requests
  48. "uptime"; -- Report how long server has been running
  49. "time"; -- Let others know the time here on this server
  50. "ping"; -- Replies to XMPP pings with pongs
  51. "register"; -- Allow users to register on this server using a client and change passwords
  52. --"mam"; -- Store messages in an archive and allow users to access it
  53. --"csi_simple"; -- Simple Mobile optimizations
  54. -- Admin interfaces
  55. "admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
  56. --"admin_telnet"; -- Opens telnet console interface on localhost port 5582
  57. -- HTTP modules
  58. --"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
  59. --"websocket"; -- XMPP over WebSockets
  60. --"http_files"; -- Serve static files from a directory over HTTP
  61. -- Other specific functionality
  62. --"limits"; -- Enable bandwidth limiting for XMPP connections
  63. --"groups"; -- Shared roster support
  64. --"server_contact_info"; -- Publish contact information for this service
  65. --"announce"; -- Send announcement to all online users
  66. --"welcome"; -- Welcome users who register accounts
  67. --"watchregistrations"; -- Alert admins of registrations
  68. --"motd"; -- Send a message to users when they log in
  69. --"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
  70. --"proxy65"; -- Enables a file transfer proxy service which clients behind NAT can use
  71. }
  72. -- These modules are auto-loaded, but should you want
  73. -- to disable them then uncomment them here:
  74. modules_disabled = {
  75. -- "offline"; -- Store offline messages
  76. -- "c2s"; -- Handle client connections
  77. -- "s2s"; -- Handle server-to-server connections
  78. -- "posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
  79. }
  80. -- Disable account creation by default, for security
  81. -- For more information see https://prosody.im/doc/creating_accounts
  82. allow_registration = false
  83. -- Force clients to use encrypted connections? This option will
  84. -- prevent clients from authenticating unless they are using encryption.
  85. c2s_require_encryption = true
  86. -- Force servers to use encrypted connections? This option will
  87. -- prevent servers from authenticating unless they are using encryption.
  88. s2s_require_encryption = true
  89. -- Force certificate authentication for server-to-server connections?
  90. s2s_secure_auth = false
  91. -- Some servers have invalid or self-signed certificates. You can list
  92. -- remote domains here that will not be required to authenticate using
  93. -- certificates. They will be authenticated using DNS instead, even
  94. -- when s2s_secure_auth is enabled.
  95. --s2s_insecure_domains = { "insecure.example" }
  96. -- Even if you disable s2s_secure_auth, you can still require valid
  97. -- certificates for some domains by specifying a list here.
  98. --s2s_secure_domains = { "jabber.org" }
  99. -- Select the authentication backend to use. The 'internal' providers
  100. -- use Prosody's configured data storage to store the authentication data.
  101. authentication = "internal_hashed"
  102. -- Select the storage backend to use. By default Prosody uses flat files
  103. -- in its configured data directory, but it also supports more backends
  104. -- through modules. An "sql" backend is included by default, but requires
  105. -- additional dependencies. See https://prosody.im/doc/storage for more info.
  106. --storage = "sql" -- Default is "internal"
  107. -- For the "sql" backend, you can uncomment *one* of the below to configure:
  108. --sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
  109. --sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
  110. --sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
  111. -- Archiving configuration
  112. -- If mod_mam is enabled, Prosody will store a copy of every message. This
  113. -- is used to synchronize conversations between multiple clients, even if
  114. -- they are offline. This setting controls how long Prosody will keep
  115. -- messages in the archive before removing them.
  116. archive_expires_after = "1w" -- Remove archived messages after 1 week
  117. -- You can also configure messages to be stored in-memory only. For more
  118. -- archiving options, see https://prosody.im/doc/modules/mod_mam
  119. -- Logging configuration
  120. -- For advanced logging see https://prosody.im/doc/logging
  121. log = {
  122. info = "prosody.log"; -- Change 'info' to 'debug' for verbose logging
  123. error = "prosody.err";
  124. -- "*syslog"; -- Uncomment this for logging to syslog
  125. -- "*console"; -- Log to the console, useful for debugging with daemonize=false
  126. }
  127. -- Uncomment to enable statistics
  128. -- For more info see https://prosody.im/doc/statistics
  129. -- statistics = "internal"
  130. -- Certificates
  131. -- Every virtual host and component needs a certificate so that clients and
  132. -- servers can securely verify its identity. Prosody will automatically load
  133. -- certificates/keys from the directory specified here.
  134. -- For more information, including how to use 'prosodyctl' to auto-import certificates
  135. -- (from e.g. Let's Encrypt) see https://prosody.im/doc/certificates
  136. -- Location of directory to find certificates in (relative to main config file):
  137. certificates = "certs"
  138. -- HTTPS currently only supports a single certificate, specify it here:
  139. --https_certificate = "/usr/local/etc/prosody/certs/localhost.crt"
  140. ----------- Virtual hosts -----------
  141. -- You need to add a VirtualHost entry for each domain you wish Prosody to serve.
  142. -- Settings under each VirtualHost entry apply *only* to that host.
  143. VirtualHost "${PROSODY_DOMAIN}"
  144. --VirtualHost "example.com"
  145. -- certificate = "/path/to/example.crt"
  146. ------ Components ------
  147. -- You can specify components to add hosts that provide special services,
  148. -- like multi-user conferences, and transports.
  149. -- For more information on components, see https://prosody.im/doc/components
  150. ---Set up a MUC (multi-user chat) room server on conference.example.com:
  151. --Component "conference.example.com" "muc"
  152. --- Store MUC messages in an archive and allow users to access it
  153. --modules_enabled = { "muc_mam" }
  154. ---Set up an external component (default component port is 5347)
  155. --
  156. -- External components allow adding various services, such as gateways/
  157. -- transports to other networks like ICQ, MSN and Yahoo. For more info
  158. -- see: https://prosody.im/doc/components#adding_an_external_component
  159. --
  160. --Component "gateway.example.com"
  161. -- component_secret = "password"
  162. interfaces = { '${PROSODY_JAIL_IP}' }