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:
Maximilian Grimm 2026-09-02 19:51:35 +02:00
parent 8cebf425c6
commit 80d5b00b67
5 changed files with 213 additions and 1 deletions

View file

@ -1,7 +1,7 @@
# ~$ selfhostedops — copy me: cp .env.example .env
# Generate secrets with: openssl rand -hex 32
# Your base domain. Services live at git.* wiki.* vault.* status.* n8n.* vpn.*
# Your base domain. Services live at git.* wiki.* vault.* status.* ntfy.* vpn.*
# DNS: one wildcard A (and AAAA) record *.ops.example.com -> your server IP
DOMAIN=ops.example.com
@ -46,3 +46,9 @@ WGEASY_PASSWORD_HASH=
RUNNER_SECRET=
RUNNER_UUID=
# --- ntfy push notifications (episode 6) ---
# No secrets here: ntfy keeps its users in its own database. Create them once:
# docker compose exec -e NTFY_PASSWORD=<pw> ntfy ntfy user add --role=user kuma
# docker compose exec ntfy ntfy access kuma alerts write-only
# See monitoring/README.md for the full walkthrough.