Skip to content
BAM Engineering Docs

Environments

There is one environment, staging, until BAM has beta users. Its names all carry ba-staging.

Hostname Serves Managed by
app.staging.businessaffairs.com The Cloudflare Pages production deployment of ba-client (built from main) Cloudflare DNS, by hand (import pending)
app.businessaffairs.com, app.demo.businessaffairs.com The same Pages production deployment Cloudflare DNS, by hand
api.staging.businessaffairs.com ca-ba-staging-api, DNS-only CNAME to the app’s Azure hostname, managed certificate to 2027-05 cloudflare and compute layers
auth.businessaffairs.com Ory Network Ory

Until 2026-11-05 app.staging pointed at the Pages branch alias master, frozen at a September build. If the client looks old or shows a mock “Username” login with no way to Ory, check the DNS record’s target first: it must be ba-client.pages.dev.

Looking at the apps

Section titled “Looking at the apps”

Every command takes --subscription ba-staging, because the default subscription on an operator’s machine may be another product’s.

Terminal window
# Which revision is live and what image it runs
az containerapp revision list -n ca-ba-staging-api -g rg-ba-staging \
  --subscription ba-staging -o table \
  --query "[].{Name:name,Running:properties.runningState,\
Traffic:properties.trafficWeight,\
Image:properties.template.containers[0].image}"


# The application's own log (JSON lines from pino)
az containerapp logs show -n ca-ba-staging-api -g rg-ba-staging \
  --subscription ba-staging --type console --tail 200


# The platform's view: pulls, probes, restarts, revision events
az containerapp logs show -n ca-ba-staging-api -g rg-ba-staging \
  --subscription ba-staging --type system --tail 100

Replace ca-ba-staging-api with ca-ba-staging-docbuilder for the document builder. Older logs are in the Log Analytics workspace law-ba-staging, tables ContainerAppConsoleLogs_CL and ContainerAppSystemLogs_CL.

az containerapp exec needs a terminal and runs from a laptop, not from an automation sandbox.

Database

Section titled “Database”

MongoDB Atlas project for BA in TEP’s Atlas organisation, Flex cluster ba-staging, database ba-api. The connection string is the vault secret MONGO-URL; read it only with an active PIM role, and never paste it anywhere. The IP access list is open because a consumption Container Apps environment has no fixed egress.

Cost

Section titled “Cost”

The design target is under USD 100 a month for staging. Check Cost analysis on the subscription; nothing in this environment has a fixed network cost.