counterweight/personal_infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: mark Uptime Kuma as decommissioned

Browse source 
README, both setup guides and the forgejo-runner notes now point at
archive/uptime_kuma/ instead of describing a live service.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
counterweight 2026-09-11 22:43:56 +02:00
parent 338f2ae636
commit 8a3fddbe49
Signed by: counterweight
GPG key ID: 883EDBAA726BD96C
4 changed files with 16 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

6
01_infra_setup.md
View file

@ -162,6 +162,12 @@ Note that, by applying these playbooks, both the root user and the `counterweigh
```bash
cp ansible/infra_secrets.yml.example ansible/infra_secrets.yml
```
> **DEPRECATED (2026-09-11).** Uptime Kuma has been decommissioned. The server
> deployment was removed from this repo; what it monitored and how it was set up is
> preserved in [`archive/uptime_kuma/`](archive/uptime_kuma/). The monitoring blocks in
> the playbooks are kept but inert (`uptime_kuma_enabled: false`) so the check logic
> survives for whatever replaces it. The credentials below no longer exist in the vault.
* Edit `ansible/infra_secrets.yml` and add your Uptime Kuma credentials:
```yaml
uptime_kuma_username: "admin"

6
02_vps_core_services_setup.md
View file

@ -49,6 +49,12 @@ Checklist:
## Uptime Kuma
> **DEPRECATED (2026-09-11).** Uptime Kuma has been decommissioned. The server
> deployment was removed from this repo; what it monitored and how it was set up is
> preserved in [`archive/uptime_kuma/`](archive/uptime_kuma/). The monitoring blocks in
> the playbooks are kept but inert (`uptime_kuma_enabled: false`) so the check logic
> survives for whatever replaces it. The credentials below no longer exist in the vault.
Uptime Kuma gets used to monitor the availability of services, keep track of their uptime and notify issues.
### Deploy

2
README.md
View file

@ -22,7 +22,7 @@ Assumes that you've set `ansible/.vault_pass` with `chmod 600`.
+ Plan install
+ File based config
+ Crossbackup to Desky via rsync
* Uptime Kuma
* ~~Uptime Kuma~~ — decommissioned 2026-09-11, see `archive/uptime_kuma/`
+ Deployed on Vipy
+ Crossbackup to Desky via rsync
* Vaultwarden

4
ansible/services/forgejo-runner/SETUP.md
View file

@ -25,4 +25,6 @@ ansible-playbook ansible/services/forgejo-runner/deploy_forgejo_runner_playbook.
1. On the VM: `systemctl status forgejo-runner` should show active
2. In Forgejo: **Site Administration** > **Actions** > **Runners** should show the runner as online
3. In Uptime Kuma: the `forgejo-runner-healthcheck` push monitor should be receiving pings
3. ~~In Uptime Kuma: the `forgejo-runner-healthcheck` push monitor should be receiving pings~~
*(Uptime Kuma was decommissioned 2026-09-11 — this check no longer applies. The
healthcheck timer still runs on the host but pushes nowhere. See `archive/uptime_kuma/`.)*