| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Normally these paths are injected into the installed 'prosody'
executable as absolute paths, but it is possible to override at least
the config path via environment variable or command line argument. This
makes sure a path relative to pwd stays relative to that instead of the
data directory.
|
| | |
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
local variable
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
util/paths at the setup_plugindir function
|
| | |
| | |
| | |
| | | |
package.path and package.cpath
|
| | |
| | |
| | |
| | | |
custom plugins exists, and creates it if it doesn't
|
| | |
| | |
| | |
| | | |
default/specified path for custom plugins
|
| | | |
|
| | |
| | |
| | |
| | | |
directories and creates them
|
|/ /
| |
| |
| | |
Taken care of by loggingmanager now
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
| |
This chancged in 6e24a69b03af likely because of confusion about the
`reopen-log-files` event which was fired but never hooked.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
2fdeb979cc7c)
|
|
|
|
| |
(which is how it used to work)
|
|
|
|
| |
(silences warning about CFG_PLUGINDIR)
|
|
|
|
| |
plugin_paths is unset
|
| |
|
|
|
|
| |
loggingmanager to simplify startup dependencies
|
|
|
|
| |
loggingmanager to reduce dependencies
|
|
|
|
| |
net.server are shown
|
| |
|
| |
|
|
|
|
| |
might not exist until loggingmanager has been loaded
|
|
|
|
| |
the global util.events instance)
|
|
|
|
| |
functions
|
|
|
|
| |
(fixes #1117)
|
| |
|
|
|
|
| |
avoid GC
|
| |
|
| |
|
| |
|
| |
|