JumpStart AMS Deployment

AMS deploys as two apps: backend API/worker/scheduler/migration releases and a standalone Next.js frontend.

Local Ports

Backend local start:

cp .env.example .env.local
./manage-ams-backend.sh up --build

Frontend local start:

npm ci
cp .env.example .env.local
npm run dev

Database Migration

The backend uses Alembic. Run local schema changes with:

./manage-ams-backend.sh run --rm migrate

Azure Helmfile runs the migrate release first. That release executes alembic upgrade head as a Helm-managed job, and the webserver, worker, and scheduler releases depend on it.

Deployed URLs

Each environment exposes the backend API and the frontend portal on their own hosts:

The frontend image takes its public configuration as Docker build arguments: NEXT_PUBLIC_API_BASE_URL (the deployed backend API URL; defaults to http://localhost:8300), NEXT_PUBLIC_COSMOS_ENABLED, NEXT_PUBLIC_COSMOS_ORG_ID, and NEXT_PUBLIC_THEMING_ENABLED. The frontend image is built on Node.js 22 and serves on port 3002.

Config Ownership

Production and cloud secrets must come from Azure Key Vault or the environment secret store. Do not commit populated .env.local files.

Verification

Backend:

uv run --extra dev ruff check .
uv run --extra dev mypy src
uv run --extra dev pytest

Frontend:

npm run build
npm run test:project-tenancy
npm run smoke:cosmos-oauth