1 -- Prosody Example Configuration File
\r
3 -- If it wasn't already obvious, -- starts a comment, and all
\r
4 -- text after it is ignored by Prosody.
\r
6 -- The config is split into sections, a global section, and one
\r
7 -- for each defined host that we serve. You can add as many host
\r
8 -- sections as you like.
\r
10 -- Lists are written { "like", "this", "one" }
\r
11 -- Lists can also be of { 1, 2, 3 } numbers, etc.
\r
12 -- Either commas, or semi-colons; may be used
\r
15 -- A table is a list of values, except each value has a name. An
\r
16 -- example would be:
\r
18 -- logging = { type = "html", directory = "/var/logs", rotate = "daily" }
\r
20 -- Whitespace (that is tabs, spaces, line breaks) is insignificant, so can
\r
21 -- be placed anywhere
\r
22 -- that you deem fitting. Youcouldalsoremoveitentirely,butforobviousrea
\r
23 --sonsIdon'trecommendit.
\r
25 -- Tip: You can check that the syntax of this file is correct when you have finished
\r
26 -- by running: luac -p prosody.cfg.lua
\r
27 -- If there are any errors, it will let you know what and where they are, otherwise it
\r
30 -- The only thing left to do is rename this file to remove the .dist ending, and fill in the
\r
31 -- blanks. Good luck, and happy Jabbering!
\r
33 -- Global settings go in this section
\r
36 -- This is the list of modules Prosody will load on startup.
\r
37 -- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
\r
39 "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
\r
40 "legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
\r
41 "roster"; -- Allow users to have a roster. Recommended ;)
\r
42 "register"; -- Allow users to register on this server using a client
\r
43 "tls"; -- Add support for secure TLS on c2s/s2s connections
\r
44 "vcard"; -- Allow users to set vCards
\r
45 "private"; -- Private XML storage (for room bookmarks, etc.)
\r
46 "version"; -- Replies to server version requests
\r
47 "dialback"; -- s2s dialback support
\r
48 "disco"; -- Service discovery
\r
49 "ping"; -- XMPP Ping
\r
50 "time"; -- Let others know the time here
\r
51 "uptime"; -- Uptime reporting
\r
52 "console"; -- telnet to port 5528 (needs console_enabled = true)
\r
55 -- These are the SSL/TLS-related settings. If you don't want
\r
56 -- to use SSL/TLS, you may comment or remove this
\r
58 key = "certs/localhost.key";
\r
59 certificate = "certs/localhost.cert";
\r
62 -- This allows clients to connect to localhost. No harm in it.
\r
65 -- Section for example.com
\r
66 -- (replace example.com with your domain name)
\r
68 -- Assign this host a certificate for TLS, otherwise it would use the one
\r
69 -- set in the global section (if any).
\r
70 -- Note that old-style SSL on port 5223 only supports one certificate, and will always
\r
71 -- use the global one.
\r
73 key = "certs/example.com.key";
\r
74 certificate = "certs/example.com.crt";
\r
77 enabled = false -- This will disable the host, preserving the config, but denying connections
\r