Files

T

Julien LutranandClaude Fable 5 a0e3a7dd86 doc: split per-host READMEs, gitea cross-repo links, consistency pass

- nuc/README.md and ks4/README.md carry the host sections (+ network
  flows) that lived in the top-level README; links rebased
- top README: repo links (doc/scripts on git.lutran.fr), index points
  at the new per-host pages
- cross-repo references now use https://git.lutran.fr/julien/scripts
  instead of relative ../scripts paths that resolve nowhere
- plakar-s3-data.md and plakar-incus-integration.md marked SUPERSEDED
  / RETIRED with pointers to restic-backup.md; their measurements and
  rationale kept
- install.md, local-backup-cron.md, incus-copy.md: crontab sections
  updated to the live schedule (01:00 replicas, 05:00 restic, Sun
  maintenance); retired legs labelled as such
- restic-backup.md: status live, cutover recorded, post-GC memory
  estimate, seed plan dated
- seafile-gc.md: online GC noted, stale 'crons commented out' removed
- ks2/: what-ks2-does-today rewritten (nothing writes to it any more),
  legs table and gates reflect restic, decommission steps updated
- db-exclude replaces the plakar-era config name (script keeps a
  fallback)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-08-28 16:04:07 +02:00

1.5 KiB

Raw Blame History

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, storage, instances
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).

1.5 KiB Raw Blame History

Personal infrastructure notes

Conventions

1.5 KiB

Raw Blame History