[#319] Added platypush/config/systemd
directory.
All checks were successful
continuous-integration/drone/push Build is passing
All checks were successful
continuous-integration/drone/push Build is passing
It contains both `platypush.service` and the `sysusers.d` and `tmpfiles.d` configurations used by the package managers.
This commit is contained in:
parent
1cad0394ab
commit
4038ef3bc1
|
@ -2,5 +2,6 @@ recursive-include platypush/backend/http/webapp/dist *
|
|||
recursive-include platypush/install *
|
||||
include platypush/plugins/http/webpage/mercury-parser.js
|
||||
include platypush/config/*.yaml
|
||||
include platypush/config/systemd/*
|
||||
global-include manifest.json
|
||||
global-include components.json.gz
|
||||
|
|
|
@ -1,30 +0,0 @@
|
|||
# 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
|
||||
# Uncomment this line if you're running the service as a privileged user
|
||||
# Requires=redis.service
|
||||
|
||||
[Service]
|
||||
ExecStart=/usr/bin/platypush
|
||||
Restart=always
|
||||
RestartSec=10
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
1
examples/systemd/platypush.service
Symbolic link
1
examples/systemd/platypush.service
Symbolic link
|
@ -0,0 +1 @@
|
|||
../../platypush/config/systemd/platypush.service
|
1
platypush/config/systemd/platypush-sysusers.conf
Normal file
1
platypush/config/systemd/platypush-sysusers.conf
Normal file
|
@ -0,0 +1 @@
|
|||
u platypush - "A general-purpose platform for automation-as-code" /var/lib/platypush
|
2
platypush/config/systemd/platypush-tmpfile.conf
Normal file
2
platypush/config/systemd/platypush-tmpfile.conf
Normal file
|
@ -0,0 +1,2 @@
|
|||
d /var/lib/platypush 0755 platypush platypush -
|
||||
d /etc/platypush 2750 platypush platypush -
|
30
platypush/config/systemd/platypush.service
Normal file
30
platypush/config/systemd/platypush.service
Normal file
|
@ -0,0 +1,30 @@
|
|||
# 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
|
||||
# Uncomment this line if you're running the service as a privileged user
|
||||
# Requires=redis.service
|
||||
|
||||
[Service]
|
||||
ExecStart=/usr/bin/platypush
|
||||
Restart=always
|
||||
RestartSec=10
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
Loading…
Reference in a new issue