No description
Find a file
counterweight 532974634e
playbooks: stop re-runs overwriting live config
Three seeding tasks used copy without force: false, so every run replaced the
real file with the starter one:

- personal-blog: the placeholder index.html over the deployed site.
- lnbits: .env.example over .env - a new AUTH_SECRET_KEY, logging every
  user out, and it would have clobbered a restored .env.
- forgejo: a two-line app.ini stub over the real config, losing
  INTERNAL_TOKEN, the JWT secrets, the DB path and ROOT_URL.

All three now seed a fresh install only. Found while restoring each from
backup on 2026-10-17.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-19 22:10:23 +02:00
ansible playbooks: stop re-runs overwriting live config 2026-10-19 22:10:23 +02:00
scripts navidrome: a music server on its own box, with beets in front of it 2026-09-27 11:09:40 +02:00
tofu/nodito jar-lid-archive: a staging deployment on its own box 2026-10-03 23:56: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 ntfy-emergency-app: remove it 2026-10-19 22:10:22 +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

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)