Workflows and deployment
GitHub Actions
Section titled “GitHub Actions”The repository already uses GitHub Actions workflows for its deployed surfaces. Each workflow follows the same broad shape:
- check out the repository
- install dependencies or SDKs
- build the target surface
- authenticate to Azure
- deploy the build artifact or container
API deployment
Section titled “API deployment”The API deployment workflow builds a container from api/Dockerfile, pushes it to GHCR, and deploys it to Azure App Service.
Frontend deployment pattern
Section titled “Frontend deployment pattern”The web properties use a Node-based App Service deployment flow that:
- runs
npm ci - builds the site
- deploys the resulting bundle with
azure/webapps-deploy
Docs site deployment
Section titled “Docs site deployment”The docs site follows the same model. Its Astro Node adapter produces a standalone server bundle in docs/dist, making it suitable for Azure App Service hosting.
Configuration guidance
Section titled “Configuration guidance”- Put secrets in GitHub Secrets, App Service configuration, or managed identity flows.
- Keep public client identifiers in build-time variables only when they are intended to be public.
- Do not commit local secrets or environment-specific private values.
Operating guidance
Section titled “Operating guidance”- Validate the surface you touched with its existing build command.
- Keep workflow changes narrow and per-surface.
- When changing API contracts, build or verify every affected client as practical.