Comparison

prosody.cfg.lua.dist @ 12345:013dcf34e8e6

prosody.cfg.lua.dist: Reword plugin_paths to de-emphasize Prosody's source dir The previous wording may contribute to people trying to install custom modules to Prosody's source directory instead of adding to plugin_paths.
author Matthew Wild <mwild1@gmail.com>
date Wed, 02 Mar 2022 14:27:05 +0000
parent 12344:4f2e77185db4
child 12346:2b5806c092f9
comparison
equal deleted inserted replaced
12344:4f2e77185db4 12345:013dcf34e8e6
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 25
26 -- Prosody will always look in its source directory for modules, but 26 -- You can use this option allows you to specify additional locations where Prosody
27 -- this option allows you to specify additional locations where Prosody 27 -- will first look for modules. For community modules, see https://modules.prosody.im/
28 -- will look for modules first. For community modules, see https://modules.prosody.im/
29 --plugin_paths = {} 28 --plugin_paths = {}
30 29
31 -- This is the list of modules Prosody will load on startup. 30 -- 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. 31 -- It looks for mod_modulename.lua in the plugins folder, so make sure that exists too.
33 -- Documentation for bundled modules can be found at: https://prosody.im/doc/modules 32 -- Documentation for bundled modules can be found at: https://prosody.im/doc/modules