archy/apps/immich-redis/manifest.yml

app:
  id: immich-redis
  name: Immich Redis
  version: "7-alpine"
  description: Valkey (Redis-compatible) cache for Immich.

  # Container named immich_redis (underscore) to match runtime per-app references
  # and serve as the server's REDIS_HOSTNAME alias on archy-net.
  container_name: immich_redis

  container:
    image: 146.59.87.168:3000/lfg2025/valkey:7-alpine
    pull_policy: if-not-present
    network: archy-net

  dependencies: []

  resources:
    memory_limit: 128Mi

  security:
    capabilities: [SETGID, SETUID]
    readonly_root: false
    network_policy: isolated

  ports: []

  volumes: []

  environment: []

  health_check:
    type: tcp
    endpoint: localhost:6379
    interval: 30s
    timeout: 5s
    retries: 3
feat(immich): scaffold registry manifests for postgres/redis/server (not yet live) immich becomes a manifest-driven stack (the legacy install_immich_stack — hardcoded podman run + sudo chown — is the anti-pattern being retired). Three image-only manifests modelled on the btcpay stack + the live .228 container config: - immich-postgres / immich-redis / immich-server on archy-net; container_name set to the underscore form (immich_postgres/_redis/_server) so the server's DB_HOSTNAME/REDIS_HOSTNAME aliases resolve. - generated_secrets: [immich-db-password] (idempotent — reuses the live secret on existing nodes; postgres is already initialised with it). - server depends on postgres+redis (install ordering); upload bind preserved. Inert for now: not added to the UI catalog and install_immich_stack still the default, so nothing installs these until the orchestrator wiring + on-node ownership (data_uid) validation lands. Schema validated by the all-manifests round-trip test. See docs/PRODUCTION-MASTER-PLAN.md §6. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 2026-06-21 05:53:58 -04:00			`app:`
			`id: immich-redis`
			`name: Immich Redis`
			`version: "7-alpine"`
			`description: Valkey (Redis-compatible) cache for Immich.`

fix(immich): name containers underscore to match runtime lifecycle code package.stop/start/restart broke ("no containers found" / "no such object immich_postgres") because the runtime hardcodes the immich stack's container names as immich_server/immich_postgres/immich_redis (underscore) across 8 files (lifecycle, health, crash-recovery, ports, config). The migration had named the containers by app_id (hyphen), mismatching all of it. Root cause of the earlier failed attempt: container_name was nested under an `extensions:` block, but `app.extensions` is serde(flatten) — container_name must be a TOP-LEVEL app key to be read by compute_container_name. Fixed: set container_name: immich_server / immich_postgres / immich_redis at top level, and point DB_HOSTNAME/REDIS_HOSTNAME at the underscore aliases. App ids stay hyphen (immich/immich-postgres/immich-redis) so the catalog identity (title+icon) holds. Manifest-only change — container names now match existing runtime references, no code edits to the 8 files. (Deriving stack containers from manifests instead of hardcoded lists remains a north-star follow-up.) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 2026-06-21 09:20:38 -04:00			`# Container named immich_redis (underscore) to match runtime per-app references`
			`# and serve as the server's REDIS_HOSTNAME alias on archy-net.`
			`container_name: immich_redis`
feat(immich): scaffold registry manifests for postgres/redis/server (not yet live) immich becomes a manifest-driven stack (the legacy install_immich_stack — hardcoded podman run + sudo chown — is the anti-pattern being retired). Three image-only manifests modelled on the btcpay stack + the live .228 container config: - immich-postgres / immich-redis / immich-server on archy-net; container_name set to the underscore form (immich_postgres/_redis/_server) so the server's DB_HOSTNAME/REDIS_HOSTNAME aliases resolve. - generated_secrets: [immich-db-password] (idempotent — reuses the live secret on existing nodes; postgres is already initialised with it). - server depends on postgres+redis (install ordering); upload bind preserved. Inert for now: not added to the UI catalog and install_immich_stack still the default, so nothing installs these until the orchestrator wiring + on-node ownership (data_uid) validation lands. Schema validated by the all-manifests round-trip test. See docs/PRODUCTION-MASTER-PLAN.md §6. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> 2026-06-21 05:53:58 -04:00
			`container:`
			`image: 146.59.87.168:3000/lfg2025/valkey:7-alpine`
			`pull_policy: if-not-present`
			`network: archy-net`

			`dependencies: []`

			`resources:`
			`memory_limit: 128Mi`

			`security:`
			`capabilities: [SETGID, SETUID]`
			`readonly_root: false`
			`network_policy: isolated`

			`ports: []`

			`volumes: []`

			`environment: []`

			`health_check:`
			`type: tcp`
			`endpoint: localhost:6379`
			`interval: 30s`
			`timeout: 5s`
			`retries: 3`