Skip to content

Conversation

@TineoC
Copy link
Collaborator

@TineoC TineoC commented Feb 1, 2026

Description

Single PR that fixes deploy/API/CI for sandbox + live.

Included:

Frontend and environment: The frontend uses relative API URLs (baseURL = ""), so one image works for both environments: when running on sandbox (balancer.sandbox.k8s.phl.io) it calls that host; when running on live (balancerproject.org) it calls that host. No env-specific build or config required.

Not closed: #451 (sanitizer) – unrelated; left open.

GitOps CD and manual deploy: Deploy: Downstream now has explicit permissions and a target input for workflow_dispatch (both | sandbox | live). CD: push to develop → Containers: Publish → deploy PR to cfp-sandbox-cluster. Live: publish release → deploy PR to cfp-live-cluster. Manual: run Deploy: Downstream with a tag (and optional target) to open deploy PRs without waiting for develop/release. Jobs were failing due to missing permissions and token; BOT_GITHUB_TOKEN must have write access to both cluster repos (see docs/DEPLOY_RESOLUTION_STEPS.md).

Other: SPA catch-all always registered (serve index.html at request time or 404). Removed .env.production and unused VITE_API_BASE_URL from frontend .env.

Related

Reviewers

@chris (for deploy/secrets follow-up; see docs/DEPLOY_RESOLUTION_STEPS.md)

- Add trailing newline to frontend/.env.production (lint)
- Clarify apiClient baseURL comment for sandbox/production
- Add Frontend: Lint and Build workflow on develop
- Add docs/DEPLOY_RESOLUTION_STEPS.md for PR follow-up
- devbox.json: use kind-config.yaml (file exists as .yaml)
- deploy/manifests/balancer/overlays/kind: overlay with secretGenerator
  for balancer-config (SQLite) so kind runs without PostgreSQL
- deploy/kind-test.sh: create cluster, install ingress, build/load image,
  apply kind overlay, wait for deployment, curl API and verify status
…, manual deploy

- Deploy: Downstream: add permissions (contents, actions, pull-requests), add
  workflow_dispatch target (both|sandbox|live) for manual deploy; CD to
  sandbox on develop, live on release; manual run opens PRs to cluster repos
- Remove frontend/.env.production and VITE_API_BASE_URL from .env (relative URLs)
- SPA catch-all: always register, serve index.html at request time or 404
- Docs: README/CLAUDE/MIGRATION/DEPLOY_RESOLUTION_STEPS and PR body
@TineoC TineoC changed the title fix: deploy API and CI for sandbox + live (closes #450, #452) fix: deploy API and CI for sandbox + live Feb 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant