Sven laptop
635a130f0b
### Summary of Changes
1. Documentation Consolidation:
• Relocated the docs/ folder and all repository .md files (README.md, DEPLOYMENT.md, DOCKER_README.md,
DOMAINS_README.md, GETTING_STARTED.md, CI_CD_PORTAINER_GUIDE.md, ADMIN_DEPLOYMENT_SUMMARY.md,
SECURITY_PRIVATE_FILES.md, handoff.md, azure-project-plan.md, plus service-specific READMEs) into .
• Updated document links in README.md.
2. AI Agent Project Map:
• Created PROJECT_MAP.md in the project root containing complete architecture diagrams, service specs, ports, DB
schemas, environment variables, and developer workflows.
• Added PROJECT_MAP.md to .gitignore.
3. Monitoring UI & Infrastructure Integration:
• Added monitoring_ui service to docker-compose.yml (port 5175).
• Configured Gitea workflow docker-build.yml for monitoring_ui builds.
• Added CORS middleware headers in index.js.
• Added nginx.conf copy step in Dockerfile.
──────
### Recommended Commit Message
docs: consolidate project documentation into monitoring_ui and add agent project map
- Move all markdown documentation files and docs/ folder into monitoring_ui/docs/
- Update documentation hub index (monitoring_ui/docs/README.md) with relative paths
- Generate comprehensive AI agent reference map (PROJECT_MAP.md) in repository root
- Add PROJECT_MAP.md and monitoring_ui build output/env overrides to .gitignore
- Integrate monitoring_ui service into docker-compose.yml and Gitea CI workflow
- Configure CORS handling in employee_api for monitoring dashboard access
──────
### Alternative Short Commit Message
refactor(docs): move docs to monitoring_ui and create AI agent PROJECT_MAP.md
1.9 KiB
Important: This skill provides guidance and recommended instructions to assist the AI system. Outputs are not guaranteed to be complete, correct, secure, or applicable to every scenario. Results should be reviewed and validated by a human before being applied. The AI model may choose not to follow all instructions exactly, and additional verification may be required.
Bicep — Static Web Apps Patterns
SWA-specific Bicep patterns. For shared patterns (skeleton, naming, tags, security defaults, data modules), see bicep-patterns.md.
Module Template
SWA modules for token-based deploys (no GitHub CI/CD):
resource staticWebApp 'Microsoft.Web/staticSites@2023-12-01' = {
name: swaName
location: location
tags: tags
sku: { name: 'Standard', tier: 'Standard' }
properties: {} // ⛔ MUST be empty — no repositoryUrl, no branch, no buildProperties
}
⛔ Standard SKU minimum — Free SWA is not offered. Free Static Web Apps lack the configuration these apps need (custom authentication, configurable CORS, SLA, private endpoints, BYO API backends via managed identity). Always emit
sku: { name: 'Standard', tier: 'Standard' }.
⛔ The API must allow this SWA's origin. A SWA calling a Function App or App Service is cross-origin, so the backend needs
siteConfig.cors.allowedOriginscontaininghttps://${staticWebApp.properties.defaultHostname}. Nothing on the SWA resource itself fixes this. Omitting it deploys cleanly and then fails every browser call withNo 'Access-Control-Allow-Origin' header is present. See bicep-patterns.md § Cross-Origin (CORS).
⛔ Detached SWA deploy: Omit
repositoryUrl,branch, andbuildPropertiesentirely. These are only for GitHub Actions–connected deployments. IncludingrepositoryUrl: ''causesBadRequest: RepositoryUrl is invalid.