counterweight/personal_infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
135 commits 4 branches 1 tag 1.5 MiB
Find a file
counterweight 7e4a7c850d
gatus: turn Signal alerting off estate-wide, with one key 
A stopgap, committed so it is visible rather than a surprise: THE PHONE IS
CURRENTLY OFF. Flip `enabled` back to true under the signal provider's
default-alert to turn it on.

Why one key reaches all ~90 endpoints: Gatus merges a provider's default-alert
into each endpoint's alert for every field the endpoint left unset, and
`enabled` is the only alert field no registration playbook sets. So this works
without editing a single endpoint and without unregistering anything. The
dashboard keeps checking and keeps showing red; it just stops sending.

Deliberately NOT done by deleting the `signal:` provider block. That would
strand ~90 endpoints referencing a provider that no longer exists, and throw
away the number and the recipient list with it.

The thing that made this necessary - a 5-minute poll turning one wedged service
into 83 messages in six hours - is fixed properly in the preceding commit. This
key is the blunt instrument that bought time to do that, and it should be
turned back on once the cadence change has been observed for a few days.

Known consequence while it is off: nothing pages. A six-day xmrblocks outage
went unannounced precisely because of this.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-27 11:08:46 +02:00
ansible gatus: turn Signal alerting off estate-wide, with one key 2026-09-27 11:08:46 +02:00
scripts xmrblocks: the Monero explorer, built off-box because 2 GB cannot compile it 2026-09-20 17:06:30 +02:00
tofu/nodito xmrblocks: the Monero explorer, built off-box because 2 GB cannot compile it 2026-09-20 17:06:30 +02:00
.gitignore tofu: stop gitignoring the lock file and the VM inventory 2026-09-12 18:43:14 +02:00
01_infra_setup.md docs: mark Uptime Kuma as decommissioned 2026-09-11 22:43:56 +02:00
02_vps_core_services_setup.md docs: mark Uptime Kuma as decommissioned 2026-09-11 22:43:56 +02:00
03_vm_disk_enlargement.md little thingies 2026-03-22 21:25:08 +01:00
README.md docs: mark Uptime Kuma as decommissioned 2026-09-11 22:43:56 +02:00
requirements.txt uptime-kuma: annotate config and drop the unused collection 2026-09-11 22:43:56 +02:00

README.md

Personal infra

My repo documenting my personal infra, along with artifacts, scripts, etc.

How to use

Go through the different numbered markdowns in the repo root to do the different parts.

How to edit secrets

ansible-vault edit ansible/your_file_with_secrets.yml

Assumes that you've set ansible/.vault_pass with chmod 600.

Overview

Services

  • Reverse Proxy
    • Deployed on Vipy
    • Caddy
    • Plan install
    • File based config
    • Crossbackup to Desky via rsync
  • Uptime Kuma — decommissioned 2026-09-11, see archive/uptime_kuma/
    • Deployed on Vipy
    • Crossbackup to Desky via rsync
  • Vaultwarden
    • Deployed on Desky
    • Crossbackup to Vipy via rsync
  • Gitea
    • Deployed on Desky
    • Crossbackup to Vipy via rsync
  • Immich
    • Deployed on Desky
  • VPN
    • All set up on Vipy
  • Bitcoin Knots
    • Deployed on Desky
  • electrs
  • Synapse Server
  • Phoenix D + LNBits
  • Backups

Infra

  • Laptop (Lapy)
  • One beefy desktop (Desky)
  • One VPS (Vipy)