prosody.cfg.lua 6.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153
  1. -- Prosody Example Configuration File
  2. --
  3. -- Information on configuring Prosody can be found on our
  4. -- website at http://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: luac -p prosody.cfg.lua
  8. -- If there are any errors, it will let you know what and where
  9. -- they are, otherwise it will keep quiet.
  10. --
  11. -- The only thing left to do is rename this file to remove the .dist ending, and fill in the
  12. -- blanks. Good luck, and happy Jabbering!
  13. ---------- Server-wide settings ----------
  14. -- Settings in this section apply to the whole server and are the default settings
  15. -- for any virtual hosts
  16. -- This is a (by default, empty) list of accounts that are admins
  17. -- for the server. Note that you must create the accounts separately
  18. -- (see http://prosody.im/doc/creating_accounts for info)
  19. -- Example: admins = { "user1@example.com", "user2@example.net" }
  20. admins = { }
  21. -- Enable use of libevent for better performance under high load
  22. -- For more information see: http://prosody.im/doc/libevent
  23. --use_libevent = true;
  24. -- This is the list of modules Prosody will load on startup.
  25. -- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
  26. -- Documentation on modules can be found at: http://prosody.im/doc/modules
  27. modules_enabled = {
  28. -- Generally required
  29. "roster"; -- Allow users to have a roster. Recommended ;)
  30. "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
  31. "tls"; -- Add support for secure TLS on c2s/s2s connections
  32. "dialback"; -- s2s dialback support
  33. "disco"; -- Service discovery
  34. -- Not essential, but recommended
  35. "private"; -- Private XML storage (for room bookmarks, etc.)
  36. "vcard"; -- Allow users to set vCards
  37. -- These are commented by default as they have a performance impact
  38. --"privacy"; -- Support privacy lists
  39. --"compression"; -- Stream compression (Debian: requires lua-zlib module to work)
  40. -- Nice to have
  41. "version"; -- Replies to server version requests
  42. "uptime"; -- Report how long server has been running
  43. "time"; -- Let others know the time here on this server
  44. "ping"; -- Replies to XMPP pings with pongs
  45. "pep"; -- Enables users to publish their mood, activity, playing music and more
  46. "register"; -- Allow users to register on this server using a client and change passwords
  47. -- Admin interfaces
  48. "admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
  49. --"admin_telnet"; -- Opens telnet console interface on localhost port 5582
  50. -- HTTP modules
  51. --"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
  52. --"http_files"; -- Serve static files from a directory over HTTP
  53. -- Other specific functionality
  54. "posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
  55. --"groups"; -- Shared roster support
  56. --"announce"; -- Send announcement to all online users
  57. --"welcome"; -- Welcome users who register accounts
  58. --"watchregistrations"; -- Alert admins of registrations
  59. --"motd"; -- Send a message to users when they log in
  60. --"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
  61. };
  62. https_ports = { }
  63. -- These modules are auto-loaded, but should you want
  64. -- to disable them then uncomment them here:
  65. modules_disabled = {
  66. -- "offline"; -- Store offline messages
  67. -- "c2s"; -- Handle client connections
  68. -- "s2s"; -- Handle server-to-server connections
  69. };
  70. -- Disable account creation by default, for security
  71. -- For more information see http://prosody.im/doc/creating_accounts
  72. allow_registration = false;
  73. daemonize = false;
  74. pidfile = "/config/data/prosody.pid";
  75. -- Force clients to use encrypted connections? This option will
  76. -- prevent clients from authenticating unless they are using encryption.
  77. c2s_require_encryption = false
  78. -- Force certificate authentication for server-to-server connections?
  79. -- This provides ideal security, but requires servers you communicate
  80. -- with to support encryption AND present valid, trusted certificates.
  81. -- NOTE: Your version of LuaSec must support certificate verification!
  82. -- For more information see http://prosody.im/doc/s2s#security
  83. s2s_secure_auth = false
  84. -- Many servers don't support encryption or have invalid or self-signed
  85. -- certificates. You can list domains here that will not be required to
  86. -- authenticate using certificates. They will be authenticated using DNS.
  87. --s2s_insecure_domains = { "gmail.com" }
  88. -- Even if you leave s2s_secure_auth disabled, you can still require valid
  89. -- certificates for some domains by specifying a list here.
  90. --s2s_secure_domains = { "jabber.org" }
  91. -- Select the authentication backend to use. The 'internal' providers
  92. -- use Prosody's configured data storage to store the authentication data.
  93. -- To allow Prosody to offer secure authentication mechanisms to clients, the
  94. -- default provider stores passwords in plaintext. If you do not trust your
  95. -- server please see http://prosody.im/doc/modules/mod_auth_internal_hashed
  96. -- for information about using the hashed backend.
  97. authentication = "internal_plain"
  98. -- Select the storage backend to use. By default Prosody uses flat files
  99. -- in its configured data directory, but it also supports more backends
  100. -- through modules. An "sql" backend is included by default, but requires
  101. -- additional dependencies. See http://prosody.im/doc/storage for more info.
  102. --storage = "sql" -- Default is "internal" (Debian: "sql" requires one of the
  103. -- lua-dbi-sqlite3, lua-dbi-mysql or lua-dbi-postgresql packages to work)
  104. -- For the "sql" backend, you can uncomment *one* of the below to configure:
  105. --sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
  106. --sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
  107. --sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
  108. -- Logging configuration
  109. -- For advanced logging see http://prosody.im/doc/logging
  110. --
  111. -- Debian:
  112. -- Logs info and higher to /var/log
  113. -- Logs errors to syslog also
  114. log = {
  115. { levels = {min = "info"}, to = "console"};
  116. }
  117. component_interface = { "*" }
  118. data_path = "/config/data"
  119. Include "conf.d/*.cfg.lua"