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