Staging Environment — Live Status

Executive Summary

In brief: Current staging URLs and open steps.

Why it matters: One-page readiness check.

Cost: Included in staging budget.

Status: Staging online.

Decision needed: None — status report

Executive Overview — all summaries for decision-makers.

As of: 2026-08-03

Render Resources (MQA Group)

Project: MQA Governance Portal (prj-d9ofcgjncjis73bu7960)

Environment	Environment ID	Resources
Production	evm-d9ofcgjncjis73bu796g	mqa-backend, mqa-frontend
Staging	evm-d9ofcgjncjis73bu7970	mqa-backend-staging, mqa-frontend-staging

Resource	ID	URL	In project
Postgres (Prod)	dpg-d9oectjl550s73ace0m0-a	Dashboard	⚠️ assign manually
Postgres (Staging)	dpg-d9of9rvqj5pc738l4qn0-a	Dashboard	⚠️ assign manually
Backend (Prod)	srv-d9oed83l550s73aceomg	https://api.mqa.group	✅ Production
Frontend (Prod)	srv-d9oectjl550s73ace0hg	https://portal.mqa.group	✅ Production
Backend (Staging)	srv-d9of9u7lk1mc738fvnb0	https://mqa-backend-staging.onrender.com	✅ Staging
Frontend (Staging)	srv-d9ofa00ae00c73bao770	https://mqa-frontend-staging.onrender.com	✅ Staging

Postgres note: Render does not allow moving existing Postgres instances into a project via API (immutable). Assignment only in Dashboard: service list → select Postgres → Move → choose environment (if available in UI).

Git Branch

• Branch: develop → auto-deploy to staging services
• Production: main → mqa-backend, mqa-frontend

Completed ✅

• [x] develop branch created on GitHub
• [x] Staging Postgres (mqa-postgres-staging, Frankfurt, basic-1gb)
• [x] Staging backend + frontend services (deploy from develop)
• [x] Base env vars (CORS, JWT, CRON, VITE_*)
• [x] Integration env copied from production (OAuth, R2, AI, email)
• [x] OAUTH_REDIRECT_URI → https://staging.api.mqa.group/api/auth/callback
• [x] DNS: staging.portal.mqa.group, staging.api.mqa.group (Hostinger CNAME → Render, verified 2026-08-04)

Manual Steps Required ⚠️

1. Connect database (2 min)

Render Dashboard → mqa-backend-staging → Environment → Add from Database → mqa-postgres-staging → save & redeploy.

Without this step, DATABASE_URL is missing and backend startup fails.

2. Azure AD redirect URI

In the MQA Azure tenant, open the app registration and add redirect URI:

https://staging.api.mqa.group/api/auth/callback

3. DNS (Hostinger)

Host	CNAME target	Status
staging.portal	mqa-frontend-staging.onrender.com	✅ Live (2026-08-04)
staging.api	mqa-backend-staging.onrender.com	✅ Live (2026-08-04)

Custom domains verified on Render; TLS certificates issued automatically.

4. Staging data

Option A: Empty DB — after link, only prisma migrate deploy (runs in entrypoint)
Option B: Prod snapshot — BACKUP-RESTORE-RUNBOOK on staging DB

Smoke Test (after DB link)

curl -sf https://staging.api.mqa.group/health
curl -sf https://staging.portal.mqa.group/

See DEPLOYMENT-CHECKLIST.

Blueprint (optional)

For IaC sync, a second blueprint instance with render-staging.yaml can be added in the Dashboard. Services already exist — blueprint then serves sync only, not initial provisioning.