1 -- Prosody Example Configuration File
\r
3 -- If it wasn't already obvious, -- starts a comment, and all
\r
4 -- text after it on a line 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, and other things.
\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 table would be:
\r
18 -- ssl = { key = "keyfile.key", certificate = "certificate.cert" }
\r
20 -- Whitespace (that is tabs, spaces, line breaks) is mostly insignificant, so
\r
22 -- be placed anywhere that you deem fitting.
\r
24 -- Tip: You can check that the syntax of this file is correct when you have finished
\r
25 -- by running: luac -p prosody.cfg.lua
\r
26 -- If there are any errors, it will let you know what and where they are, otherwise it
\r
29 -- The only thing left to do is rename this file to remove the .dist ending, and fill in the
\r
30 -- blanks. Good luck, and happy Jabbering!
\r
32 -- Server-wide settings go in this section
\r
35 -- This is the list of modules Prosody will load on startup.
\r
36 -- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
\r
38 -- Generally required
\r
39 "roster"; -- Allow users to have a roster. Recommended ;)
\r
40 "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
\r
41 "tls"; -- Add support for secure TLS on c2s/s2s connections
\r
42 "dialback"; -- s2s dialback support
\r
43 "disco"; -- Service discovery
\r
45 -- Not essential, but recommended
\r
46 "private"; -- Private XML storage (for room bookmarks, etc.)
\r
47 "vcard"; -- Allow users to set vCards
\r
50 "legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
\r
51 "version"; -- Replies to server version requests
\r
52 "uptime"; -- Report how long server has been running
\r
53 "time"; -- Let others know the time here on this server
\r
54 "ping"; -- Replies to XMPP pings with pongs
\r
55 "pep"; -- Enables users to publish their mood, activity, playing music and more
\r
56 "register"; -- Allow users to register on this server using a client and change passwords
\r
58 -- Other specific functionality
\r
59 --"posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
\r
60 --"console"; -- telnet to port 5582 (needs console_enabled = true)
\r
61 --"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
\r
62 --"httpserver"; -- Serve static files from a directory over HTTP
\r
65 -- These modules are auto-loaded, should you
\r
66 -- for (for some mad reason) want to disable
\r
67 -- them then uncomment them below
\r
68 modules_disabled = {
\r
74 -- Disable account creation by default, for security
\r
75 -- For more information see http://prosody.im/doc/creating_accounts
\r
76 allow_registration = false;
\r
78 -- These are the SSL/TLS-related settings. If you don't want
\r
79 -- to use SSL/TLS, you may comment or remove this
\r
81 key = "certs/localhost.key";
\r
82 certificate = "certs/localhost.cert";
\r
85 -- This allows clients to connect to localhost. No harm in it.
\r
88 -- Section for example.com
\r
89 -- (replace example.com with your domain name)
\r
92 enabled = false -- This will disable the host, preserving the config, but denying connections
\r
94 -- Assign this host a certificate for TLS, otherwise it would use the one
\r
95 -- set in the global section (if any).
\r
96 -- Note that old-style SSL on port 5223 only supports one certificate, and will always
\r
97 -- use the global one.
\r
99 key = "certs/example.com.key";
\r
100 certificate = "certs/example.com.crt";
\r
103 -- Set up a MUC (multi-user chat) room server on conference.example.com:
\r
104 Component "conference.example.com" "muc"
\r