How alucrece/deploiement_continu works
Project type and purpose
• This is a full-stack web application with a React frontend (“my-app”) and a Python backend (“server”).
• It includes database schema migrations (SQLFiles), local orchestration (docker-compose), and a CI/CD pipeline (GitHub Actions, Codecov, GitHub Pages).
• The README focuses on the React side (Create React App), test coverage, and automatic GitHub Pages deployment.
File structure
• Top level:
• .github/ – CI workflows.
• docker-compose.yml – local dev orchestration.
• SQLFiles/ – migration scripts for the database.
• my-app/ – React client, tests (Jest + React Testing Library + Cypress), build config, Dockerfile.
• server/ – Python service (server.py), Dockerfile, requirements, test coverage report, Vercel config.
• Patterns:
• Two distinct microservices (frontend, backend).
• SQL migrations as a separate component.
• CI/CD workflows trigger on push and PR.
• Containerization for reproducible dev and production.
README for additional insights
• Describes:
• React scripts (start, test, build, eject).
• Test coverage of 100%.
• GitHub Actions steps: install, test, coverage, Codecov upload, build, deploy front-end.
• Mentions E2E tests via Cypress (optional).
Elements
• Blue for user-facing components (Browser, SPA)
• Green for compute services (API, CI runner)
• Orange for data stores (DB, migrations)
• Grey for external services (GitHub Actions, Codecov, GitHub Pages)