Preserve Photos deployment configuration and verify source dependencies

2026-10-08 19:25:37 +08:00
parent bb452649b8
commit 0b9b548d20
5 changed files with 100 additions and 0 deletions
@@ -301,3 +301,23 @@ and change the workflow pin. All validation steps remain unchanged.
 Python toolcache misses may still require setup-python to download Python from
 its upstream release source. This removes Action source download dependence,
 not every possible external download. No Runner or NAS network configuration is changed.
+
+### Synology Photos dependencies
+
+For a production photo source using Synology Photos person filtering, configure
+`SYNOLOGY_PHOTOS_URL` and `SYNOLOGY_PHOTOS_CERT_SHA256` as Gitea Variables. The
+certificate fingerprint must match the configured HTTPS endpoint. Keep the Photos
+session in the persistent `/config` directory; never put session credentials in
+Variables or repository files.
+
+`PROD_PHOTOS_DIR` must identify the actual NAS photo directory mounted read-only
+at `/photos`. Adoption requires that mount to exist on the current container;
+changing this Variable alone does not create a new mount. Existing supplementary
+permission groups are preserved by deployment.
+
+Restoring SQLite and session files does not restore these runtime dependencies.
+Production smoke checks now reject an enabled people-filtered source if its
+Photos configuration or stored connection is missing. These checks do not prove
+session validity or scan the complete catalog: after restoring a source, also
+verify its read-only `/api/v1/photo-sources/{id}/images?limit=1` endpoint before
+running an automation task.