Skip to content
Snippets Groups Projects
Commit 6066dae0 authored by Robin Appelman's avatar Robin Appelman
Browse files

put systemd autorestart in a <details> section


Signed-off-by: default avatarRobin Appelman <robin@icewind.nl>
parent 15bc857c
No related branches found
No related tags found
No related merge requests found
......@@ -105,7 +105,10 @@ Every time this app receives an update you should restart the systemd service us
`sudo systemctl restart notify_push`
Alternatively, you can do this automatically via systemctl by creating the following systemd service and path:
<details>
<summary>Alternatively, you can do this automatically via systemctl by creating the following systemd service and path (click to expand)</summary>
First create a oneshot service to trigger the daemon restart
`/etc/systemd/system/notify_push-watcher.service`
```ini
......@@ -125,6 +128,8 @@ ExecStart=/usr/bin/systemctl restart notify_push.service
WantedBy=multi-user.target
```
Then create a `path` job to trigger the restart whenever the push binary is changed
`/etc/systemd/system/notify_push-watcher.path`
```ini
[Unit]
......@@ -142,6 +147,14 @@ WantedBy=multi-user.target
Adjusting the path as needed.
Finally, enable it with
```bash
sudo systemctl enable notify_push-watcher.path
```
</details>
### Reverse proxy
It is **strongly** recommended to set up the push service behind a reverse proxy, this both removes the need to open
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment