| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | util.prosodyctl.shell: Allow passing path to socket on command line | Kim Alvefur | 2020-06-01 | 1 | -1/+1 | |
| | | | | | E.g. `prosodyctl shell --socket /path/to/prosody.scok` | |||||
| * | util.prosodyctl.shell: Use same config option as module for socket path | Kim Alvefur | 2020-06-01 | 1 | -1/+2 | |
| | | | | | | So now if you set it to a custom value, both the client and the server should use it. | |||||
| * | util.prosodyctl.shell: Join socket path with current data directory | Kim Alvefur | 2020-06-01 | 1 | -1/+3 | |
| | | | | | | | Don't hardcode socket path as it happens to be in a source checkout. Hold on, it should use the same config option as the module! | |||||
| * | mod_admin_shell, mod_admin_telnet, util.prosodyctl.shell: Separate output ↵ | Matthew Wild | 2020-06-01 | 1 | -2/+4 | |
| | | | | | | | from final result Fixes the client pausing for input after output from commands. | |||||
| * | prosodyctl, util.prosodyctl.shell: `prosodyctl shell` - a client to access ↵ | Matthew Wild | 2020-06-01 | 1 | -0/+125 | |
| the prosodyctl admin shell | ||||||
 |
index : prosody.git | |
| unofficial mirror of the prosody mercurial project |
| aboutsummaryrefslogtreecommitdiffstats |