| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
certificates everywhere (thanks jasperixla)
|
|
|
|
| |
warnings if no LuaSec installed)
|
| |
|
| |
|
| |
|
|
|
|
| |
state (Thanks Florob)
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
|/
|
|
| |
modules setting globals
|
| |
|
| |
|
| |
|
|
|
|
| |
certificate commands
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
various other stuff
|
|
|
|
| |
default plugin path
|
| |
|
|
|
|
| |
can be used outside of prosodyctl itself
|
|
|
|
| |
prosody.paths.data always contains the correct value (including config)
|
|
|
|
| |
installed
|
|
|
|
| |
global
|
|
|
|
| |
dependencies so we can check hard deps before the config and logging is loaded
|
| |
|
| |
|
|
|
|
| |
main prosody executable.
|
|
|
|
| |
to match main prosody executable.
|
|
|
|
| |
config parsers (to match the main prosody executable).
|
|
|
|
| |
already running
|
| |
|
|
|
|
| |
attempt is made to query Prosody's status (thanks stever)
|
| |
|