Comparison

prosody.cfg.lua.dist @ 12344:4f2e77185db4

prosody.cfg.lua.dist: Remove network_backend option The only sensible option for most people these days is "epoll". The option is still supported, but it should only be needed by packagers for specific platforms (e.g. BSD may choose libevent for kqueue) or other special cases.
author Matthew Wild <mwild1@gmail.com>
date Wed, 02 Mar 2022 14:22:02 +0000
parent 12343:310bd427901c
child 12345:013dcf34e8e6
comparison
equal deleted inserted replaced
12343:310bd427901c 12344:4f2e77185db4
20 -- This is a (by default, empty) list of accounts that are admins 20 -- This is a (by default, empty) list of accounts that are admins
21 -- for the server. Note that you must create the accounts separately 21 -- for the server. Note that you must create the accounts separately
22 -- (see https://prosody.im/doc/creating_accounts for info) 22 -- (see https://prosody.im/doc/creating_accounts for info)
23 -- Example: admins = { "user1@example.com", "user2@example.net" } 23 -- Example: admins = { "user1@example.com", "user2@example.net" }
24 admins = { } 24 admins = { }
25
26 -- Prosody includes several alternative modules for keeping track of network connections.
27 -- For more information see: https://prosody.im/doc/network_backend
28 --network_backend = "epoll"
29 25
30 -- Prosody will always look in its source directory for modules, but 26 -- Prosody will always look in its source directory for modules, but
31 -- this option allows you to specify additional locations where Prosody 27 -- this option allows you to specify additional locations where Prosody
32 -- will look for modules first. For community modules, see https://modules.prosody.im/ 28 -- will look for modules first. For community modules, see https://modules.prosody.im/
33 --plugin_paths = {} 29 --plugin_paths = {}