Support multiple instances with systemd, defaults to 'sopel' #1059
Conversation
|
I don't have much experience with systemd, so it'd be great if someone with experience could review this. |
There was a problem hiding this comment.
From what I know of systemd, this is a straightforward change. The only concern I have is for existing users, who will have to be told to move their configuration from /etc/sopel.cfg to /etc/sopel/sopel.cfg. For all I know, systemd has a way to perform such a migration automatically; I haven't looked very hard yet. But whether it's addressed by the unit file itself or by a note in the changelog, it will have to be addressed (separately, because the source repo of this PR no longer exists).
|
Why not both? We can keep With a bit of documentation, I think this should be fine! |
The source fork no longer exists, so this was rebased & merged locally to fix conflicts and address PR feedback. GitHub may or may not recognize the PR as merged, because the commit hash changed.
|
Decided to use a small part of my Sunday morning on fixing this up. Merged by f2838a0 in modified form, leaving the original |
Usage:
systemctl start sopel@sopel