tegwick
48a5e6eac0
helm/core-hub-values.yaml was the last file still pulling from gitea.coulomb.social. Both hostnames resolve, but to different machines - gitea.coulomb.social to 92.205.130.254 (CoulombCore) and forgejo.coulomb.social to 92.205.62.239 (Railiance01) - so this quietly deployed core-hub from the frozen CoulombCore registry rather than failing loudly. Every other values file in this repo, including charts/core-hub/values.yaml for the same app, already used forgejo. The tag is a render-time placeholder; deploys pass CORE_HUB_IMAGE_TAG=<sha>, so the next core-hub rollout must confirm that sha is present on the Forgejo registry before promoting. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
17 lines
No EOL
530 B
YAML
17 lines
No EOL
530 B
YAML
# Production overrides for the core-hub Helm chart.
|
|
# Non-secret values only; CORE_HUB_DATABASE_URL and CORE_HUB_API_TOKEN come from
|
|
# the Secret 'core-hub-prod-env' in the core-hub namespace.
|
|
|
|
image:
|
|
repository: forgejo.coulomb.social/coulomb/core-hub
|
|
tag: "production-placeholder" # Render baseline only; deploy requires CORE_HUB_IMAGE_TAG=<sha>.
|
|
|
|
runtime:
|
|
coreHubEnv: production
|
|
autoCreateTables: "0"
|
|
configMapName: core-hub-prod-runtime
|
|
|
|
envSecretName: core-hub-prod-env
|
|
|
|
migration:
|
|
jobName: core-hub-prod-migrate |