docs(plan): append gitea ci/cd pipeline requirements
This commit is contained in:
@@ -11,6 +11,7 @@
|
||||
- **Frontend**: Next.js with Bun
|
||||
- **Deployment (prod)**: Kubernetes cluster
|
||||
- **Deployment (local)**: Docker Compose
|
||||
- **New request**: Append CI/CD pipeline planning for the Gitea-hosted repository (`https://code.hal9000.damnserver.com/MasterMito/work-club-manager`)
|
||||
|
||||
## Technical Decisions
|
||||
- **Multi-tenancy strategy**: RLS + EF Core global query filters (defense-in-depth)
|
||||
@@ -51,9 +52,16 @@
|
||||
## Decisions (Round 4)
|
||||
- **Git repository**: Initialize git repo as first step in Task 1 — `git init` + comprehensive `.gitignore` (dotnet + node + IDE) + initial commit
|
||||
|
||||
## Decisions (Round 5)
|
||||
- **CI/CD requested**: User wants plan extension for pipeline on Gitea server
|
||||
- **Repository host**: Self-hosted Gitea instance (`code.hal9000.damnserver.com`)
|
||||
- **Pipeline scope**: CI-only (no deployment automation in this extension)
|
||||
- **Release policy input**: User prefers release-tag based trigger if CD is added later
|
||||
- **Registry input**: Gitea Container Registry preferred
|
||||
|
||||
## Open Questions
|
||||
- (none remaining — all critical decisions made, ready for plan generation)
|
||||
- (none blocking — CI scope confirmed; CD trigger/registry captured for future extension)
|
||||
|
||||
## Scope Boundaries
|
||||
- INCLUDE: Full backend API, frontend app, Docker Compose, Kubernetes manifests (Kustomize), database schema + EF Core migrations, Keycloak integration, work item CRUD, time-slot shift management with sign-up, club-switcher, role-based access control (4 roles), PostgreSQL RLS
|
||||
- INCLUDE: Full backend API, frontend app, Docker Compose, Kubernetes manifests (Kustomize), database schema + EF Core migrations, Keycloak integration, work item CRUD, time-slot shift management with sign-up, club-switcher, role-based access control (4 roles), PostgreSQL RLS, Gitea CI workflow (build/test/lint/manifest validation)
|
||||
- EXCLUDE: Billing/subscriptions, email/push notifications, mobile app, recurring shift patterns (future), custom roles, reporting/analytics dashboard
|
||||
|
||||
Reference in New Issue
Block a user