GRMrGecko/service-notifications
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Compare commits

base: GRMrGecko:ef253e214a48178a5e606f353d84b0c43da485d8
Branches Tags
GRMrGecko:main
GRMrGecko:v0.3
GRMrGecko:v0.2
GRMrGecko:v0.1
..
compare: GRMrGecko:ca1612f3837de8631abf28225d00a7fe87beb3ea
Branches Tags
GRMrGecko:main
GRMrGecko:v0.3
GRMrGecko:v0.2
GRMrGecko:v0.1

No commits in common. "ef253e214a48178a5e606f353d84b0c43da485d8" and "ca1612f3837de8631abf28225d00a7fe87beb3ea" have entirely different histories.
ef253e214a ... ca1612f383

1 changed files with 4 additions and 4 deletions
Show Stats Expand all files Collapse all files

8
README.md
View File

@ -16,7 +16,7 @@ go build
### Running as a service
You are likely going to want to run the tool as a service to ensure it runs at boot and restarts in case of failures. Below is an example service config file you can place in `/etc/systemd/system/service-notifications.service` on a linux system to run as a service if you install the binary in `/usr/local/bin/`.
You are likely going to want to run the tool as a service to ensure it runs at boot and restarts in case of failures. Below is an example service config file you can place in `/etc/systemd/system/midi-request-trigger.service` on a linux system to run as a service if you install the binary in `/usr/local/bin/`.
```systemd
[Unit]
@ -75,17 +75,17 @@ On MacOS, you can setup a Launch Agent in `~/Library/LaunchAgents/com.mrgeckosme
Start with:
```bash
launchctl load ~/Library/LaunchAgents/com.mrgeckosmedia.service-notifications.plist
launchctl load ~/Library/LaunchAgents/com.mrgeckosmedia.midi-request-trigger.plist
```
Check status with:
```bash
launchctl list com.mrgeckosmedia.service-notifications
launchctl list com.mrgeckosmedia.midi-request-trigger
```
Stop with:
```bash
launchctl unload ~/Library/LaunchAgents/com.mrgeckosmedia.service-notifications.plist
launchctl unload ~/Library/LaunchAgents/com.mrgeckosmedia.midi-request-trigger.plist
```
## Cron job