Sven laptop
635a130f0b
Build and Push Docker Images / detect-changes (push) Successful in 11s
Build and Push Docker Images / build-auth-api (push) Successful in 1m0s
Build and Push Docker Images / build-employee-api (push) Successful in 1m2s
Build and Push Docker Images / build-transit-api (push) Successful in 1m1s
Build and Push Docker Images / build-error-log-api (push) Successful in 1m5s
Build and Push Docker Images / build-admin-ui (push) Successful in 1m13s
Build and Push Docker Images / build-monitoring-ui (push) Successful in 1m15s
Build and Push Docker Images / deploy-test-node (push) Successful in 3s
### 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
48 lines
1.8 KiB
Markdown
48 lines
1.8 KiB
Markdown
<!-- 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.
|
|
|
|
# Database Migrations — Detection
|
|
|
|
When a database dependency is found, detect the migration tool so the plan can record it. The generation phase uses this to configure migration automation within the orchestrator.
|
|
|
|
---
|
|
|
|
## Detection
|
|
|
|
Scan three layers, then synthesize.
|
|
|
|
### Layer 1: Migration Files
|
|
|
|
Non-exhaustive detection pattern examples:
|
|
|
|
| Pattern | Tool |
|
|
|---------|------|
|
|
| `prisma/migrations/` | Prisma |
|
|
| `alembic/`, `alembic.ini` | Alembic |
|
|
| `**/migrations/*.py` | Django |
|
|
| `Migrations/*.cs` | EF Core |
|
|
| `flyway.conf` | Flyway |
|
|
| `migrations/*.sql` | Raw SQL |
|
|
|
|
### Layer 2: Dependencies
|
|
|
|
Check dependency manifests for migration tools, ORMs with built-in migration support, and database driver packages.
|
|
|
|
### Layer 3: Scripts
|
|
|
|
Check script runners (`package.json`, `Makefile`, etc.) for existing migration commands (grep for common migration key words like: `migrate`, `schema`, `seed`).
|
|
|
|
### Synthesis
|
|
|
|
1. Cross-reference all three layers — they should agree
|
|
2. If an existing migration command exists, use it (don't invent a new one)
|
|
3. If layers conflict, ask the user which tool is active
|
|
|
|
### Insufficient Evidence
|
|
|
|
If a database dependency exists but no migration strategy is found across all three layers:
|
|
|
|
1. Do not guess
|
|
2. Ask the user via `ask_user` how they manage schema changes
|
|
3. Record the gap in the plan's Migrations section with `⚠️ Not detected`
|