──────

### 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
2026-09-20 23:33:55 +02:00
parent f935bbeb8c
commit 635a130f0b
195 changed files with 28309 additions and 957 deletions
@@ -0,0 +1,68 @@
+<!-- azure-cor-disclaimer -->
+> **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.
+
+# {Emulator Name}
+
+> **Template** — Copy this file to `emulators/{name}.md` when adding a new emulator.
+
+---
+
+## Docker Image
+
+<!-- Official image and recommended pinned tag. -->
+
+```
+{org}/{image}:{tag}
+```
+
+## docker-compose Service Block
+
+<!-- Complete service YAML block, ready to paste. Includes ports, volumes, health check. -->
+
+```yaml
+services:
+  {service-name}:
+    image: {org}/{image}:{tag}
+    ports:
+      - "{host-port}:{container-port}"
+    volumes:
+      - ./.{service-name}:/data
+    restart: unless-stopped
+```
+
+## Connection String
+
+<!-- Default local connection string for the app to use. -->
+
+```
+{connection-string}
+```
+
+## Required App Environment Variables
+
+<!-- Variable names the app must set to point at this emulator. -->
+
+| Variable | Value |
+|----------|-------|
+| `{VAR_NAME}` | `{value}` |
+
+## Healthcheck (Database Emulators Only)
+
+<!-- If this emulator is a database, include a healthcheck block in the docker-compose service above AND document it here. The migration service (see migrations.md) depends on `condition: service_healthy` to wait for the database before running migrations. Without a healthcheck, auto-migration will not work. -->
+
+<!-- Delete this section if the emulator is not a database. -->
+
+## Container Runtime Support
+
+<!-- State whether this emulator has been certified for Docker, Podman, or both. -->
+<!-- The compose service block is engine-agnostic, but some Microsoft emulator images make Docker-specific assumptions (privileged mode, architecture, licensing). -->
+<!-- If this emulator is NOT yet certified for Podman, say so here so the generation phase emits a `⚠️ LIMITED SUPPORT` warning when the plan selects Podman. -->
+
+| Docker | Podman |
+|--------|--------|
+| {✅ certified / 🔲 planned} | {✅ certified / 🔲 planned} |
+
+## Notes
+
+<!-- Platform caveats (arm64/x86), known issues, resource requirements. -->
+<!-- Note any Podman-specific caveats here (SELinux `:Z` labels on Linux, rootless port ranges, Podman-machine bind-mount paths). -->