revil-O/platypush
1
0
Fork 0
forked from platypush/platypush
Code Pull requests Activity

systemd requirements tweak.

Browse source 
`Requires=redis.service` should be commented unless the service is
started as a privileged user.

Also added some comments on how the systemd service usually works.
This commit is contained in:
Fabio Manganiello 2024-05-20 21:51:08 +02:00
parent 02a3385638
commit 1cad0394ab
Signed by untrusted user: blacklight
GPG key ID: D90FBA7F76362774
1 changed files with 19 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
examples/systemd/platypush.service
View file

@ -1,7 +1,25 @@
# Platypush systemd service file.
#
# It is advised to install Platypush through a supported package manager or a
# Platypush Docker container.
#
# In such case, the service file should be automatically installed and configured,
# and Platypush can be started either via `[sudo] systemctl start platypush`
# (privileged start, usually with a dedicated `platypush` user) or
# `systemctl --user start platypush` if you want to run it through a generic user.
#
# In the first case, the working directory would usually be
# `/var/lib/platypush`, and the configuration will be stored under `/etc/platypush`.
#
# You can however also copy this service configuration either to
# `/etc/systemd/system/platypush.service` or
# `~/.config/systemd/user/platypush.service`.
[Unit]
Description=Platypush - A general-purpose platform for automation
After=network.target redis.service
Requires=redis.service
# Uncomment this line if you're running the service as a privileged user
# Requires=redis.service
[Service]
ExecStart=/usr/bin/platypush