unboundsoftware/schemas-app
6
0 Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Projects Releases Activity

feat: deploy to Frostmoln production #391

Merged
argoyle merged 2 commits from feat/frostmoln-production into main 2026-10-15 21:16:08 +00:00
Conversation 0 Commits 2 Files Changed 8
+65 -40
2 Commits
Author SHA1 Message Date
argoyleandClaude Opus 5.5 0f7610d03f fix: make the nginx config readable by the unprivileged user
schemas-app / build (pull_request) Successful in 4m9s
Details
schemas-app / deploy-prod-frostmoln (pull_request) Skipped
Details 
COPY keeps the source file's mode; a 600 file (local checkouts) left
uid 101 unable to read it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ma8eHhW59hLAJuLzBnLvUu
 2026-10-14 22:26:30 +02:00
argoyleandClaude Opus 5.5 1646ee1bc3 feat: deploy to Frostmoln production 
The AWS deploy-prod job has failed since CI left AWS (no k8s.unbound.se
context on the runners). Deploys now go to the Frostmoln production
cluster (namespace schemas), the way the sites do.

Frostmoln enforces restricted Pod Security: the pod runs as the image's
non-root user with a matching securityContext. The prod-only manifests
move to the prod-frostmoln target; the ALB ingress becomes a Traefik one
with a Let's Encrypt certificate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Ma8eHhW59hLAJuLzBnLvUu
 2026-10-14 22:15:38 +02:00