Files
the-pet-loft/deploy/staging/compose.yml
ianshaloom af8e14c545
Some checks failed
Deploy — Staging / Lint, Typecheck & Test (push) Successful in 1m33s
Deploy — Staging / Build & push — admin (push) Successful in 57s
Deploy — Staging / Build & push — storefront (push) Successful in 58s
Deploy — Staging / Deploy to staging VPS (push) Failing after 18s
fix(deploy): inject runtime secrets and force-recreate containers on deploy
- Add --force-recreate to podman compose up so stale containers are never
  reused across deploys when the image tag (staging) is reused
- Inject CLERK_SECRET_KEY and ADMIN_CLERK_SECRET_KEY from Gitea secrets into
  ~/staging/.env on the VPS via printf (variables expand on the runner before
  SSH, so secrets never touch VPS shell history; file gets chmod 600)
- Update compose.yml: storefront gets CLERK_SECRET_KEY, admin gets
  CLERK_SECRET_KEY mapped from ADMIN_CLERK_SECRET_KEY

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-03-08 12:42:06 +03:00

25 lines
478 B
YAML

name: petloft-staging
services:
storefront:
image: ${REGISTRY}/storefront:staging
restart: unless-stopped
ports:
- "3001:3000"
env_file:
- path: .env
required: false
environment:
- CLERK_SECRET_KEY
admin:
image: ${REGISTRY}/admin:staging
restart: unless-stopped
ports:
- "3002:3001"
env_file:
- path: .env
required: false
environment:
- CLERK_SECRET_KEY=${ADMIN_CLERK_SECRET_KEY}