deploy/server/plane.stg.env

Ref: Size: 1.9 KiB History
# stg plane values — stg.eitri.sh.
#
# The same keys as plane.prod.env, because the same templates render both. Where
# a value differs, it differs because the two planes share a cluster and a node
# — not because stg is a smaller product.

NAMESPACE=eitri-stg

NODE_NAME=vnic-1
IMAGE_ARCH=arm64

CONSOLE_HOST=stg.eitri.sh
API_HOST=api.stg.eitri.sh
GATE_HOST=gate.stg.eitri.sh
SYNC_HOST=sync.stg.eitri.sh
# stg publishes its own /dl rather than borrowing prod's: scripts/site-image.sh
# stages exactly one version into site/dist/dl, so pushing a pre-release to
# eitri.sh would 404 every released download URL in the wild. Its own origin
# also means the release artifacts, the manifest shape and the cache headers
# are rehearsed by the same script that will later do it to prod.
SITE_HOST=dl.stg.eitri.sh

# stg shares vnic-1 with prod, so it cannot share prod's host ports: a second
# hostNetwork pod claiming 8081/8443/2222 would fail to schedule or silently
# lose its listeners.
HTTP_PORT=8082
SYNC_PORT=8444
GATE_PORT=2223

# stg signs in against the bundled eitri-oidc rather than Google: the plane is
# then reproducible from nothing but this repo and a Secret, its identities are
# ours to create and delete, and the smoke can drive a real sign-in headlessly.
# What it gives up is stated in the README — prod's relying-party wiring against
# a third-party IdP is the one part of sign-in stg does not exercise.
LOCAL_OIDC=1
OIDC_HOST=oidc.stg.eitri.sh
# Not a host port: the issuer is an ordinary pod behind a Service.
OIDC_PORT=9111
OIDC_TLS_SECRET=stg-oidc-tls
OIDC_CONFIG_SECRET=eitri-stg-oidc-config
OIDC_PVC_NAME=eitri-stg-oidc-data
OIDC_PVC_SIZE=1Gi

CONFIG_SECRET=eitri-stg-server-config
PVC_NAME=eitri-stg-server-data
PVC_SIZE=2Gi
TLS_SECRET=stg-console-tls
SITE_TLS_SECRET=stg-web-tls

# No backups: stg's database is disposable by design, and a second nightly
# sqlite job against local-path storage on the same node buys nothing.
BACKUPS=0