Annotate
prosodyctl: Further deprecate start/stop/restart commands when installed
Despite the warning we introduced, many people continue to try using
prosodyctl to manage Prosody in the presence of systemctl (e.g. #1688).
Also, despite the warning, prosodyctl proceeded with the operation. This means
the commands could be invoked by accident, and cause a situation that is hard
to recover from (needing to manually track down stray processes).
This commit disables all the problematic commands by default, but this can
still be overridden using --force or via a config option.
We only perform this check when we believe Prosody has been "installed" for
system-wide use (i.e. running it from a source directory is still supported).
author |
Matthew Wild <mwild1@gmail.com> |
date |
Thu, 06 Feb 2025 14:51:31 +0000 |
parent |
5403:d7ecf6cd584e |
rev |
line source |
5403
|
1
|
|
2 The Prosody project is open to contributions (see HACKERS file), but is
|
|
3 maintained daily by:
|
94
|
4
|
5403
|
5 - Matthew Wild (mail: matthew [at] prosody.im)
|
|
6 - Waqas Hussain (mail: waqas [at] prosody.im)
|
|
7 - Kim Alvefur (mail: zash [at] prosody.im)
|
|
8
|
|
9 You can reach us collectively by email: developers [at] prosody.im
|
|
10 or in realtime in the Prosody chatroom: prosody@conference.prosody.im
|