admin/turf_saas
1
0
Fork 0
Code Issues Pull Requests 8 Actions Packages Projects Releases Wiki Activity

Sprint 7-8 — CI/CD + Docker + Monitoring (HRT-33) #4

Open
admin wants to merge 0 commits from feature/devops-cicd into master
pull from: feature/devops-cicd
merge into: admin:master
Conversation 0 Commits - Files Changed -
admin commented 2026-04-26 23:11:53 +02:00
Owner
Copy Link

Dockerfile multi-stage, docker-compose, CI/CD Gitea Actions, Prometheus/Grafana.

Dockerfile multi-stage, docker-compose, CI/CD Gitea Actions, Prometheus/Grafana.
admin added 2 commits 2026-04-26 23:11:54 +02:00
feat(devops): CI/CD + Docker + Monitoring infrastructure dce1e9b744 
- Multi-stage Dockerfile (builder+runner, <500MB target)
- docker-compose.yml: app(x4) + postgres + redis + prometheus + grafana + nginx
- .env.example with all required secrets (never hardcoded)
- requirements.txt with all dependencies including prometheus-client, alembic
- GitHub Actions CI: lint (flake8+bandit+safety) + tests + Docker build/push
- GitHub Actions CD: staging deploy -> smoke tests -> production deploy + rollback
- Alembic migration setup + initial PostgreSQL schema (001_initial_schema)
- SQLite→PostgreSQL data migration script
- Prometheus metrics module (HTTP, ML, DB, business metrics)
- Prometheus alert rules (5xx >1%, latency >2s, disk >80%, ML accuracy)
- Grafana dashboard (overview: req/s, p95, ML accuracy, error rate)
- Nginx reverse proxy config (HTTPS/TLS, rate limiting, security headers)
- Structured JSON logging module
- Automated daily DB backup script (pg_dump + 30-day retention)

Branch: feature/devops-cicd

Co-Authored-By: Paperclip <noreply@paperclip.ing>
fix(qa): add /health endpoints to Flask apps for Docker healthchecks 793ee82c29 
Docker compose healthchecks target /health on combined-api, dashboard-api
and portal, but these endpoints did not exist (returned 404). This caused
all dependent services (condition: service_healthy) to fail startup.

- combined_api.py: GET /health + /turf/health with DB connectivity check
- dashboard_api.py: GET /health + /turf/health with DB connectivity check
- portal_server.py: GET /health (lightweight, no DB)

QA Finding 1 from HRT-34 review of HRT-33 branch feature/devops-cicd.

Co-Authored-By: Paperclip <noreply@paperclip.ing>
This pull request has changes conflicting with the target branch.
  • account.html
  • dashboard_saas.html
  • landing.html
  • login.html
  • onboarding.html
  • portal_server.py
  • register.html
  • saas_api_v1.py
  • saas_auth.py
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feature/devops-cicd:feature/devops-cicd
git checkout feature/devops-cicd
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: admin/turf_saas#4
Delete Branch "feature/devops-cicd"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?