Personal infrastructure notes

Two repositories back this setup: doc (this one) and scripts (the cron drivers and their config files, deployed to /root/scripts on each host).

Start here:

• backup-strategy.md — what is backed up, by which tool, on what schedule, and how to restore.
• new-container.md — conventions for adding a service to ks4 (and getting it backed up automatically).

Tech notes

• nuc/ — home lab on nuc: host, iGPU instances
• nas/ — storage + backup host nas (Supermicro A1SAi-2750F): the 4 TB on direct SATA, media over NFS, backup pools
• ks4/ — prod server ks4 at OVH: host, services, network flows
• ks2/ — legacy backup server being decommissioned
• archer-c7/ — home router (TP-Link Archer C7 v5 running on OpenWrt)

Conventions

• One markdown file per topic in the correct subdir, containing the full implementation notes, configuration, and troubleshooting notes.
• Containers are built from Debian/Ubuntu images and configured exclusively through incus exec/incus config so the doc is the single source of truth — rebuilding = re-running the script.
• Adding a service to ks4: follow new-container.md (no Docker in containers — incus runs OCI images natively and incus-compose handles stacks; data paths go into scripts/restic-paths).