8c119efff8
- #3 Liveness probe targets full SSR DB-querying / route, coupling pod liveness to SQLite - #4 Chart values-staging/production.yaml are dead config under Flux; drift trap - #6 tsconfig includes gitignored emdash-env.d.ts that only the dev server generates - #7 Dockerfile package-lock glob + npm install fallback can silently build an unlocked image - #8 Dockerfile creates runtime user without pinning its GID - #9 entrypoint.sh gates `emdash init` on data.db absence, skipping migrations on PVC reuse - #10 pullPolicy: Always vs digest pinning - #11 Dockerfile state symlinks contradict the STATE_DIR contract; Dockerfile does not set ENV STATE_DIR - #12 astro is a production dependency, so npm prune --omit=dev keeps build-only tooling - #14 Two ImageUpdateAutomations write back to the same anton-helm-workloads main branch - #16 memoryCache provider is per-process; correctness depends implicitly on replicas:1 - #17 Root catch-all [slug].astro couples nav links to pages-collection rows + DB hit per unmatched path - #18 Detail pages render a 200-style body under a 404 status and have no try/catch around getEmDash* calls - #19 vite allowedHosts hardcodes ddev hostnames (dev-only; no prod impact)
23 lines
677 B
YAML
23 lines
677 B
YAML
# Staging overrides for DIRECT `helm upgrade -f values-staging.yaml` use only.
|
|
#
|
|
# IMPORTANT: FluxCD does NOT read this file. The live staging deploy is driven
|
|
# solely by the inline `spec.values:` block in
|
|
# deploy/fleet-overlay/cms-plugins-staging/helmrelease.yaml (copied into
|
|
# anton-helm-workloads). Editing values here has NO effect on the cluster.
|
|
# Keep this file in sync with that HR `values:` block by hand, or it will drift.
|
|
|
|
image:
|
|
tag: staging-latest
|
|
|
|
ingress:
|
|
host: cms-plugins-staging.kotkanagrilli.fi
|
|
|
|
# Slimmer staging — non-critical workload, can run lean.
|
|
resources:
|
|
requests:
|
|
cpu: 50m
|
|
memory: 192Mi
|
|
limits:
|
|
cpu: 500m
|
|
memory: 768Mi
|