Add deployment preflight and fix helium Syncthing root

2026-08-03 10:16:32 +00:00
parent 1c2590c3c8
commit 1f97faeab5
5 changed files with 230 additions and 2 deletions
@@ -16,3 +16,19 @@ placements can hardlink rather than make a full copy.
 `/media/Data2/Downloading` already contains unrelated files. The fresh qB
 instance must not import or manage them; only Archive Control-created torrents
 are managed.
+
+Before the first client start, run the repository preflight on the target host
+(replace container names if that host uses different compose project names):
+
+```sh
+python3 scripts/preflight-deployment.py \
+  --client-config ~/Repositories/compose/ArchiveControl-archive/client.toml \
+  --client-container archive-control-helium-archive-client-1 \
+  --syncthing-container helium-syncthing-syncthing-1 \
+  --qbittorrent-container helium-qbittorrent-qbittorrent-1
+```
+
+It is read-only: it checks the configured API roots resolve to the same host
+paths as the client roots, that both data roots share one client bind mount for
+hardlinks, secret-file permissions, filesystem capabilities, and the local qB
+and Syncthing APIs. It does not send the control token or modify any container.
@@ -37,6 +37,6 @@ local_root = "/data/storage/Downloading"
 [syncthing]
 endpoint = "http://127.0.0.1:8384"
 api_key_file = "/run/secrets/syncthing_api_key"
-api_root = "/var/syncthing"
+api_root = "/var/syncthing/Sync"
 local_root = "/data/storage/Sync"
 advertised_addresses = ["dynamic"]