· 9 years ago · Oct 06, 2016, 11:18 AM
1
2-- Information on configuring Prosody can be found on our
3-- website at http://prosody.im/doc/configure
4--
5-- Tip: You can check that the syntax of this file is correct
6-- when you have finished by running: luac -p prosody.cfg.lua
7-- If there are any errors, it will let you know what and where
8-- they are, otherwise it will keep quiet.
9--
10-- The only thing left to do is rename this file to remove the .dist ending, and fill in the
11-- blanks. Good luck, and happy Jabbering!
12
13daemonize = true
14pidfile = "/run/prosody/prosody.pid"
15s2s_require_encryption = false
16
17---------- Server-wide settings ----------
18-- Settings in this section apply to the whole server and are the default settings
19-- for any virtual hosts
20
21-- This is a (by default, empty) list of accounts that are admins
22-- for the server. Note that you must create the accounts separately
23-- (see http://prosody.im/doc/creating_accounts for info)
24-- Example: admins = { "user1@example.com", "user2@example.net" }
25admins = { "spark@uwtech.org" }
26
27-- Enable use of libevent for better performance under high load
28-- For more information see: http://prosody.im/doc/libevent
29--use_libevent = true;
30
31-- This is the list of modules Prosody will load on startup.
32-- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
33-- Documentation on modules can be found at: http://prosody.im/doc/modules
34modules_enabled = {
35
36 -- Generally required
37 "roster"; -- Allow users to have a roster. Recommended ;)
38 "saslauth"; -- Authentication for clients and servers. Recommended if you want to log in.
39 "tls"; -- Add support for secure TLS on c2s/s2s connections
40 "dialback"; -- s2s dialback support
41 "disco"; -- Service discovery
42
43 -- Not essential, but recommended
44 "private"; -- Private XML storage (for room bookmarks, etc.)
45 "vcard"; -- Allow users to set vCards
46
47 -- These are commented by default as they have a performance impact
48 --"privacy"; -- Support privacy lists
49 --"compression"; -- Stream compression
50
51 -- Nice to have
52 "version"; -- Replies to server version requests
53 "uptime"; -- Report how long server has been running
54 "time"; -- Let others know the time here on this server
55 "ping"; -- Replies to XMPP pings with pongs
56 "pep"; -- Enables users to publish their mood, activity, playing music and more
57 "register"; -- Allow users to register on this server using a client and change passwords
58
59 -- Admin interfaces
60 "admin_adhoc"; -- Allows administration via an XMPP client that supports ad-hoc commands
61 --"admin_telnet"; -- Opens telnet console interface on localhost port 5582
62
63 -- HTTP modules
64 --"bosh"; -- Enable BOSH clients, aka "Jabber over HTTP"
65 --"http_files"; -- Serve static files from a directory over HTTP
66
67 -- Other specific functionality
68 "posix"; -- POSIX functionality, sends server to background, enables syslog, etc.
69 --"groups"; -- Shared roster support
70 --"announce"; -- Send announcement to all online users
71 --"welcome"; -- Welcome users who register accounts
72 --"watchregistrations"; -- Alert admins of registrations
73 --"motd"; -- Send a message to users when they log in
74 --"legacyauth"; -- Legacy authentication. Only used by some old clients and bots.
75};
76
77-- These modules are auto-loaded, but should you want
78-- to disable them then uncomment them here:
79modules_disabled = {
80 -- "offline"; -- Store offline messages
81 -- "c2s"; -- Handle client connections
82 -- "s2s"; -- Handle server-to-server connections
83};
84
85-- Disable account creation by default, for security
86-- For more information see http://prosody.im/doc/creating_accounts
87allow_registration = false;
88
89-- These are the SSL/TLS-related settings. If you don't want
90-- to use SSL/TLS, you may comment or remove this
91ssl = {
92 key = "/etc/prosody/certs/uwtech.key";
93 certificate = "/etc/prosody/certs/uwtech.crt";
94}
95
96-- Force clients to use encrypted connections? This option will
97-- prevent clients from authenticating unless they are using encryption.
98
99c2s_require_encryption = true
100
101-- Force certificate authentication for server-to-server connections?
102-- This provides ideal security, but requires servers you communicate
103-- with to support encryption AND present valid, trusted certificates.
104-- NOTE: Your version of LuaSec must support certificate verification!
105-- For more information see http://prosody.im/doc/s2s#security
106
107s2s_secure_auth = false
108
109-- Many servers don't support encryption or have invalid or self-signed
110-- certificates. You can list domains here that will not be required to
111-- authenticate using certificates. They will be authenticated using DNS.
112
113--s2s_insecure_domains = { "gmail.com" }
114
115-- Even if you leave s2s_secure_auth disabled, you can still require valid
116-- certificates for some domains by specifying a list here.
117
118--s2s_secure_domains = { "jabber.org" }
119
120-- Select the authentication backend to use. The 'internal' providers
121-- use Prosody's configured data storage to store the authentication data.
122-- To allow Prosody to offer secure authentication mechanisms to clients, the
123-- default provider stores passwords in plaintext. If you do not trust your
124-- server please see http://prosody.im/doc/modules/mod_auth_internal_hashed
125-- for information about using the hashed backend.
126
127authentication = "internal_plain"
128
129-- Select the storage backend to use. By default Prosody uses flat files
130-- in its configured data directory, but it also supports more backends
131-- through modules. An "sql" backend is included by default, but requires
132-- additional dependencies. See http://prosody.im/doc/storage for more info.
133
134--storage = "sql" -- Default is "internal"
135
136-- For the "sql" backend, you can uncomment *one* of the below to configure:
137--sql = { driver = "SQLite3", database = "prosody.sqlite" } -- Default. 'database' is the filename.
138--sql = { driver = "MySQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
139--sql = { driver = "PostgreSQL", database = "prosody", username = "prosody", password = "secret", host = "localhost" }
140
141-- Logging configuration
142-- For advanced logging see http://prosody.im/doc/logging
143log = {
144 -- info = "prosody.log"; -- Change 'info' to 'debug' for verbose logging
145 -- error = "prosody.err";
146 "*syslog"; -- Uncomment this for logging to syslog
147 -- "*console"; -- Log to the console, useful for debugging with daemonize=false
148}
149
150----------- Virtual hosts -----------
151-- You need to add a VirtualHost entry for each domain you wish Prosody to serve.
152-- Settings under each VirtualHost entry apply *only* to that host.
153
154VirtualHost "localhost"
155
156VirtualHost "uwtech.org"
157 -- Assign this host a certificate for TLS, otherwise it would use the one
158 -- set in the global section (if any).
159 -- Note that old-style SSL on port 5223 only supports one certificate, and will always
160 -- use the global one.
161 ssl = {
162 key = "/etc/prosody/certs/uwtech.key";
163 certificate = "/etc/prosody/certs/uwtech.crt";
164 }
165
166------ Components ------
167-- You can specify components to add hosts that provide special services,
168-- like multi-user conferences, and transports.
169-- For more information on components, see http://prosody.im/doc/components
170
171---Set up a MUC (multi-user chat) room server on conference.example.com:
172--Component "conference.example.com" "muc"
173
174-- Set up a SOCKS5 bytestream proxy for server-proxied file transfers:
175--Component "proxy.example.com" "proxy65"
176
177---Set up an external component (default component port is 5347)
178--
179-- External components allow adding various services, such as gateways/
180-- transports to other networks like ICQ, MSN and Yahoo. For more info
181-- see: http://prosody.im/doc/components#adding_an_external_component
182--
183--Component "gateway.example.com"
184-- component_secret = "password"