Skip to content

fix(staging): set the backend's public API origin (TASK-403) #2531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
lilyshen0722 wants to merge 1 commit into from
Closed

fix(staging): set the backend's public API origin (TASK-403) #2531

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions k8s/helm/commonly/values-staging.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,6 +121,12 @@ backend:
# every /v2 page errors. The same allowlist feeds the socket.io cors. Caught by the Tier-1
# staging smoke 2026-10-23 (all /v2 renders failed on CORS until this landed).
frontendUrl: "https://staging.commonly.me"
# The backend's public API origin. It sets the Atlassian connect hint ("allow
# <origin>/** in MCP server domains") and the CIMD and callback URLs. Unset, it falls
# back to the chart default (values.yaml: https://api.commonly.me), so staging told
# users to allow prod's API host. Staging's API is api-staging.commonly.me (the
# commonly-staging tunnel's ingressRules above).
backendUrl: "https://api-staging.commonly.me"
# Staging backend runs on the SPOT pool at a fraction of prod's requests, so it fits
# the nodes we already have (spot-pool sits at single-digit % CPU) without growing a
# pool. Prod backend stays on dev-pool because it holds session state a spot
Expand Down
Loading