finished ntfy server thingies
This commit is contained in:
parent
13537aa984
commit
a41e1d9383
3 changed files with 139 additions and 1 deletions
|
|
@ -120,6 +120,25 @@ Forgejo is a git server.
|
|||
* You can tweak more settings from that point on.
|
||||
* SSH cloning should work out of the box (after you've set up your SSH pub key in Forgejo, that is).
|
||||
|
||||
|
||||
## ntfy
|
||||
|
||||
ntfy is a notifications server.
|
||||
|
||||
### Deploy
|
||||
|
||||
* Decide what subdomain you want to serve ntfy on and add it to `services/ntfy/ntfy_vars.yml` on the `ntfy_subdomain`.
|
||||
* Note that you will have to add a DNS entry to point to the VPS public IP.
|
||||
* Before running the playbook, you should decide on a user and password for the admin user. This user is the only one authorised to send and read messages from topics. Once you've picked, export them in your terminal like this `export NTFY_USER=admin; export NTFY_PASSWORD=secret`.
|
||||
* In the same shell, run the deployment playbook: `ansible-playbook -i inventory.ini services/ntfy/deploy_ntfy_playbook.yml`.
|
||||
|
||||
### Configure
|
||||
|
||||
* You can visit the ntfy web UI at the FQDN you configured.
|
||||
* You can start using notify to send alerts with uptime kuma by visiting the uptime kuma UI and using the credentials for the ntfy admin user.
|
||||
* To receive alerts on your phone, install the official ntfy app: https://github.com/binwiederhier/ntfy-android.
|
||||
* You can also subscribe on the web UI on your laptop.
|
||||
|
||||
### Backups
|
||||
|
||||
No explicit backups. It's assumed that important repos will be in Lapy, and that perhaps you might even backup lapy as well.
|
||||
Given that ntfy is almost stateless, no backups are made. If it blows up, simply set it up again.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue