Deployment
Azure Pipelines and Helm deployment for the flow-technology documentation portal.
This portal deploys as a Node container on AKS — the same pattern as skunkworks docs-app, adapted
to frontend/docs-app/.
Pipeline
frontend/docs-app/.azure/azure-pipelines.yml- Trigger paths:
frontend/docs-app - Branches:
develop→ dev,master→ prod - Image name:
flow-technology-docs
Template: frontend/docs-app/.azure/build-deploy-nodeapp-template.yml
- Build and push Docker image to ACR
helm upgrade --installon AKS
Helm chart
frontend/docs-app/.azure/k8s/ wraps the shared basicapi chart (v1.0.5).
| Environment | Host |
|---|---|
| Dev | dev-flow-technology-docs.notflow.life, dev-flow-technology-docs.apps-and-services.com |
| Prod | flow-technology-docs.notflow.life, flow-technology-docs.apps-and-services.com |
Port 3000, one replica, no runtime secrets.
Local container
docker build --tag flow-technology-docs:local frontend/docs-app
docker run --rm --publish 3000:3000 flow-technology-docs:localEdge security
The app has no authentication. DNS, TLS, and Cloudflare Access must protect the origin before enabling the pipeline in a new environment.
Service deployments
Go services use a separate pattern (SOPS secrets, migration jobs, multi-binary images). See
Template operations for the reference .azure/
layout under services/template/.azure/.