prosody.git - unofficial mirror of the prosody mercurial project

	Commit message (Collapse)	Author	Age	Files	Lines
*	util.prosodyctl.shell: Bring back banner set from config!	Kim Alvefur	2021-11-12	1	-0/+2
\| \| \| \|	I miss my custom ANSI-colored greeting!
*	util.prosodyctl.shell: Allow setting custom prompt (admin_shell_prompt)	Matthew Wild	2021-11-11	1	-4/+6
\|
*	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.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.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	1	-1/+1
\|
*	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