#707 Providing alternative configuration file on command line
Reporter
Michal Rus
Owner
Zash
Created
Updated
Stars
★ (1)
Tags
Component-Docs
Status-Fixed
Milestone-0.10
Type-Enhancement
Priority-Medium
Michal Rus
on
Description of feature:
It should be possible to provide an alternative location of the configuration file via CLI switch, as it is with other UNIX daemons.
Sample use case: Prosody service in NixOS has no way to know to be restarted, when the configuration changes, because its location is bound to /etc/prosody/prosody.cfg.lua, instead of being some file in /nix/store/, hash of which changes with each change of the file. Cf. https://github.com/NixOS/nixpkgs/blob/7475728593a49f09c4b7b959b15513aee38ab4b4/nixos/modules/services/networking/prosody.nix
Thank you!
Zash
on
Hi!
This is already possible with a --config option to either prosody (since 0.6.0) or prosodyctl (since 0.8.0 I think).
Does this solve your problem?
Changes
owner Zash
Michal Rus
on
@Zash, yes, it does solve *my* problem, indeed, thank you. :-)
However, maybe the subject of this issue should be adding this to information to:
1) manual,
2) https://prosody.im/doc/configure,
3) prosodyctl --help,
4) …?
Otherwise, how can users know about it, other than reading source code?
Thank you!
Zash
on
Changes
tags Component-Docs
Zash
on
Changes
tags Milestone-0.10 Status-Accepted
Zash
on
Changes
tags Status-Started
Zash
on
Added a line about --config here: https://prosody.im/doc/prosodyctl
No idea where to mention the flag to prosody itself, as it has no documentation anywhere. Separate issue for that perhaps.
Description of feature: It should be possible to provide an alternative location of the configuration file via CLI switch, as it is with other UNIX daemons. Sample use case: Prosody service in NixOS has no way to know to be restarted, when the configuration changes, because its location is bound to /etc/prosody/prosody.cfg.lua, instead of being some file in /nix/store/, hash of which changes with each change of the file. Cf. https://github.com/NixOS/nixpkgs/blob/7475728593a49f09c4b7b959b15513aee38ab4b4/nixos/modules/services/networking/prosody.nix Thank you!
Hi! This is already possible with a --config option to either prosody (since 0.6.0) or prosodyctl (since 0.8.0 I think). Does this solve your problem?
Changes@Zash, yes, it does solve *my* problem, indeed, thank you. :-) However, maybe the subject of this issue should be adding this to information to: 1) manual, 2) https://prosody.im/doc/configure, 3) prosodyctl --help, 4) …? Otherwise, how can users know about it, other than reading source code? Thank you!
Added a line about --config here: https://prosody.im/doc/prosodyctl No idea where to mention the flag to prosody itself, as it has no documentation anywhere. Separate issue for that perhaps.
Changes