Episode 6: Uptime Kuma monitors that mean something, ntfy push server, status page, second eye
Claude-Session: https://claude.ai/code/session_01Y1BTehJjJ4Chr6YscVRXmn
This commit is contained in:
parent
8cebf425c6
commit
80d5b00b67
5 changed files with 213 additions and 1 deletions
18
README.md
18
README.md
|
|
@ -189,6 +189,24 @@ people. Note that joining is three steps, not two: you invite, they log in,
|
|||
and then an owner has to **confirm** them. Until that confirmation, a member
|
||||
sees no shared items at all.
|
||||
|
||||
## Alerts that reach you (Episode 6)
|
||||
|
||||
A monitor nobody hears is a dashboard. Episode 6 adds a push channel you own
|
||||
(ntfy, `ntfy.<DOMAIN>`), keyword monitors for everything a customer sees,
|
||||
internal monitors for the services that left the internet in episode 5, a
|
||||
public status page at the root of `status.<DOMAIN>`, and a second Uptime Kuma
|
||||
outside the server, because a box cannot report its own death.
|
||||
|
||||
```bash
|
||||
docker compose up -d ntfy
|
||||
docker compose exec caddy caddy reload --config /etc/caddy/Caddyfile
|
||||
docker compose exec -e NTFY_PASSWORD='<pw>' ntfy ntfy user add --role=user kuma
|
||||
docker compose exec ntfy ntfy access kuma alerts write-only
|
||||
```
|
||||
|
||||
The full walkthrough, the second-eye compose file and the gotchas are in
|
||||
**[monitoring/README.md](monitoring/README.md)**.
|
||||
|
||||
## Hardening
|
||||
|
||||
Before you put real company data on this box, read **[HARDENING.md](HARDENING.md)**.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue