coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
railiance-platform/.claude/rules/stack-and-commands.md
codex 34a3123799
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Finish RAILIANCE-WP-0017 consumption-mode enforcement 
Read the resource-control open/restricted signal and refuse new orders
that would exceed a restricted entity's published allowance. Open and
missing signals stay unchanged. Safety paths admit with an exception.
2026-08-15 14:56:02 +02:00

868 B
Raw Blame History

Stack

  • Language: Kubernetes manifests + Helm values, Bash Make targets
  • Key deps: CloudNative-PG (cnpg) clusters, OpenBao, SOPS/age; runs against the S2 cluster on railiance01. Bitnami postgresql-ha is retired. Valkey is declared, not deployed.

Dev Commands

make help              # list all targets (db-*, apps-pg-*, openbao-*)
make db-status         # gitea-db / forgejo-db cnpg cluster health (read-only)
make apps-pg-status    # shared apps-pg cluster health (read-only)
make pg-status         # confirms retired Bitnami postgresql-ha is absent
make valkey-status     # confirms Valkey is absent
make consumption-preflight CONSUMING_ENTITY=entity:<slug> ESTIMATE_EUR=<eur>
make db-deploy | apps-pg-deploy   # production-touching

pg-deploy and valkey-deploy are fail-closed. *-status / *-logs targets are read-only and safe.