| Commit message (Collapse) | Author | Age | Files | Lines | ||
|---|---|---|---|---|---|---|
| ... | ||||||
| * | util.prosodyctl.check: Normalize away trailing dot in some messages too | Kim Alvefur | 2021-07-04 | 1 | -8/+13 | |
| | | ||||||
| * | util.prosodyctl.check: Normalize potential to form without trailing '.' | Kim Alvefur | 2021-07-04 | 1 | -0/+2 | |
| | | | | | | | In some cases you might end up with both 'xmpp.example.com' and 'xmpp.example.com.', which are the same thing so no point in doing the same checks twice. | |||||
| * | util.prosodyctl.check: Point out if A/AAAA exists despite disabled IPvX | Kim Alvefur | 2021-07-04 | 1 | -0/+10 | |
| | | | | | | | Clients would try to connect and receive an error or timeout, increasing the time it takes to establish a connection. Probably not what you want. If you really want IPv6 or IPv4 disabled, best remove the A or AAAA record. | |||||
| * | util.prosodyctl.check: Warn if both use_ipv4 and use_ipv6 are set to false | Kim Alvefur | 2021-07-04 | 1 | -0/+6 | |
| | | | | | Why would you do this?! | |||||
| * | util.prosodyctl.check: Silence IP protocol mismatches when disabled | Kim Alvefur | 2021-07-04 | 1 | -2/+4 | |
| | | | | | | If you set 'use_ipv4 = false' then you probably don't care much for the host not resolving to the IPv4 address, and same with 'use_ipv6'. | |||||
| * | util.prosodyctl.check: Reload unbound to ensure hosts.txt is ignored | Kim Alvefur | 2021-07-03 | 1 | -1/+3 | |
| | | | | | | | If unbound was initialized prior to this then the config change here wouldn't apply, and it will again think that 127.0.1.1 has been found in DNS. | |||||
| * | util.prosodyctl.check: Collect options from all global plugins | Kim Alvefur | 2021-05-27 | 1 | -0/+45 | |
| | | ||||||
| * | util.prosodyctl.check: Format, sort option listings into canonical form | Kim Alvefur | 2021-05-27 | 1 | -8/+34 | |
| | | | | | | Makes merges and diffs easier to read and deal with, especially when using tools to gather options from the codebase. | |||||
| * | util.prosodyctl.check: Ensure that libunbound does not check hosts file | Kim Alvefur | 2021-06-20 | 1 | -0/+3 | |
| | | | | | | | This fixes wrongly reported DNS problems on some distros where the hosts file contains an entry for the local machine, pointing at a loopback address such as 127.0.1.1 or similar. | |||||
| * | util.prosodyctl.check: Deprecate legacy_ssl related options | Kim Alvefur | 2021-06-20 | 1 | -0/+1 | |
| | | ||||||
| * | util.prosodyctl.check: Add support for checking Direct TLS SRV records | Kim Alvefur | 2021-06-20 | 1 | -1/+23 | |
| | | ||||||
| * | util.prosodyctl.check: Fix for net.dns vs unbound API difference | Kim Alvefur | 2021-06-20 | 1 | -2/+2 | |
| | | | | | | net.dns returns nil for NXDOMAIN, while net.unbound returns a table with zero items and various status fields. | |||||
| * | util.prosodyctl.check: Add knowledge of the global-only 'use_ipv4' setting | Kim Alvefur | 2021-06-20 | 1 | -1/+1 | |
| | | ||||||
| * | Merge 0.11->trunk | Kim Alvefur | 2021-05-27 | 1 | -1/+1 | |
| | | ||||||
| * | Merge 0.11->trunk | Matthew Wild | 2021-05-13 | 1 | -1/+1 | |
| | | ||||||
| * | util.prosodyctl.shell: Fix for different location of unpack in Lua 5.1 | Kim Alvefur | 2021-04-25 | 1 | -1/+2 | |
| | | ||||||
| * | util.prosodyctl.shell: Fix for missing 'sep' arg to string.rep in Lua 5.1 | Kim Alvefur | 2021-04-25 | 1 | -1/+2 | |
| | | ||||||
| * | util.prosodyctl.shell: Allow calling console commands with fewer shell quotes | Kim Alvefur | 2021-04-25 | 1 | -3/+2 | |
| | | | | | | | | | E.g. `prosodyctl shell module reload disco example.com` becomes equivalent to `prosodyctl shell 'module:reload("disco", "example.com")`. Won't work for every possible command, but reduces the amount of shell quoting problems for most common commands. | |||||
| * | util.prosodyctl.shell: Allow passing a single command as argument | Kim Alvefur | 2021-03-05 | 1 | -0/+29 | |
| | | | | | | | | | | | | | | | | | | | | | | | | | Test procedure: $ prosodyctl shell 'server:version()' Expect: > OK: hg:926d53af9a7a $ prosodyctl shell 'server:version()' 'hello' Expect: > Only one command is supported as argument $ prosodyctl shell 'lorem ipsum'; echo $? Expect: > Sorry, I couldn't understand that... console:1: syntax error near 'show' > 1 (error code) Thanks Menel for mentioning the feature | |||||
| * | util.prosodyctl.shell: Fix check for --quiet | Kim Alvefur | 2021-03-05 | 1 | -1/+1 | |
| | | | | | | | | | | | | | | Looked in the wrong table Test procedure: $ prosodyctl shell --quiet Expect: Prosody> (No banner) | |||||
| * | util.prosodyctl.check: Recognise global options related to plugin installer | Kim Alvefur | 2021-01-21 | 1 | -0/+1 | |
| | | ||||||
| * | util.prosodyctl.cert: Fix for prompt functions having moved to util.human.io | Kim Alvefur | 2020-11-09 | 1 | -3/+4 | |
| | | ||||||
| * | util.prosodyctl.check: Use net.unbound for DNS if available | Kim Alvefur | 2020-06-25 | 1 | -0/+3 | |
| | | | | | Improves performance somewhat by avoiding the rate limiting in net.dns | |||||
| * | util.prosodyctl.shell: Collect extra return values | Kim Alvefur | 2020-06-17 | 1 | -1/+1 | |
| | | | | | Forgot in previous commit | |||||
| * | util.prosodyctl.shell: Handle argument parsing errors | Kim Alvefur | 2020-06-17 | 1 | -0/+9 | |
| | | | | | | | While almost identical to the handling in util.startup, this seems more appropriate. It would also simplify if shell-specific options need to be handled in the future. | |||||
| * | util.prosodyctl.check: Fix traceback by handling SRV '.' target to | Kim Alvefur | 2020-06-14 | 1 | -0/+8 | |
| | | | | | | The IDNA to-ASCII operation returns nil in this case, which causes an error in net.dns | |||||
| * | util.prosodyctl.shell: Save readline history | Kim Alvefur | 2020-06-02 | 1 | -0/+7 | |
| | | ||||||
| * | util.prosodyctl.shell, util.adminstream: Move connection logic into ↵ | Matthew Wild | 2020-06-02 | 1 | -42/+8 | |
| | | | | | adminstream for easier reuse | |||||
| * | util.prosodyctl.shell: Really fix --socket option | Kim Alvefur | 2020-06-02 | 1 | -1/+3 | |
| | | | | | | Forgot it stops parsing --foo options at the first argument, so subsequent commands need to parse their own options like this. | |||||
| * | util.prosodyctl.shell: Correct check for --socket | Kim Alvefur | 2020-06-02 | 1 | -1/+1 | |
| | | ||||||
| * | prosodyctl+util.prosodyctl.*: Start breaking up the ever-growing prosodyctl | Matthew Wild | 2020-06-02 | 3 | -1/+824 | |
| | | ||||||
| * | 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 |