Write proper systemd / sysvinit scripts for rustodon #135
Labels
A: Flagship 🚀
pertaining to rustodon.glitch.social, the flagship instance
C: Enhancement ✨
An issue which details an improvement to the software, not necessarily to fix a bug.
Comments
barzamin
added
A: Flagship 🚀
dfgweb
added a commit
to dfgweb/rustodon
that referenced
this issue
Aug 13, 2019
In service file, assume Rustodon instance is deployed in /srv/rustodon. Include an /etc/default/rustodon environment file to define required env. To use them (as root): ``` $ cp scripts/default_rustodon /etc/default/rustodon $ cp scripts/rustodon.service /etc/systemd/system/ $ systemctl enable rustodon.service $ systemctl start rustodon.service $ journalctl -u rustodon.service ``` Variables in `/srv/rustodon/.env` may be moved in `/etc/default/rustodon`.
barzamin
added a commit
that referenced
this issue
Nov 12, 2019
Add systemd service for rustodon (#135)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current init files are written with a metric tonne of "I don't know what I'm doing". Because of this, they don't log rustodon output and possibly aren't easy to trace or programtically confirm whether they're running, expecially in the context of content delivery.
As a core developer, if Travis/CodeDeploy fails, there should be a clear artifact I can use to follow the events that lead up to the services' failure.
The text was updated successfully, but these errors were encountered: