cardosofelipe/syndarix
1
0
Fork 0
forked from cardosofelipe/fast-next-template
Code Issues 18 Pull Requests Wiki Activity

Set up complete Docker Compose for local development #21

New Issue
Closed
opened 2025-12-29 23:46:00 +00:00 by cardosofelipe · 0 comments
cardosofelipe commented 2025-12-29 23:46:00 +00:00
Owner
Copy Link

Description

Create comprehensive Docker Compose configuration for running the full Syndarix stack locally.

Requirements

Services

  1. db - PostgreSQL with pgvector
  2. redis - Cache and message broker
  3. backend - FastAPI application
  4. frontend - Next.js application
  5. celery-agent - Celery worker (agent queue)
  6. celery-git - Celery worker (git queue)
  7. celery-sync - Celery worker (sync queue)
  8. celery-default - Celery worker (default queue)

Configuration

  • Health checks for all services
  • Proper dependency ordering (depends_on with conditions)
  • Volume mounts for development (hot reload)
  • Environment variable templates
  • Resource limits (optional for dev)

Files

  • docker-compose.yaml - Main compose file
  • docker-compose.override.yaml - Development overrides
  • .env.example - Environment template

Acceptance Criteria

  • All services start with docker compose up
  • Health checks pass for all services
  • Hot reload works for backend and frontend
  • Database data persists across restarts
  • All services can communicate
  • Documented in DEVELOPMENT.md

Technical Notes

  • Reference: Issues #17 (Redis), #18 (Celery), #19 (pgvector)
  • This issue depends on #17, #18, #19 completion

Dependencies

Assignable To

devops-engineer agent

## Description Create comprehensive Docker Compose configuration for running the full Syndarix stack locally. ## Requirements ### Services 1. `db` - PostgreSQL with pgvector 2. `redis` - Cache and message broker 3. `backend` - FastAPI application 4. `frontend` - Next.js application 5. `celery-agent` - Celery worker (agent queue) 6. `celery-git` - Celery worker (git queue) 7. `celery-sync` - Celery worker (sync queue) 8. `celery-default` - Celery worker (default queue) ### Configuration - Health checks for all services - Proper dependency ordering (`depends_on` with conditions) - Volume mounts for development (hot reload) - Environment variable templates - Resource limits (optional for dev) ### Files - `docker-compose.yaml` - Main compose file - `docker-compose.override.yaml` - Development overrides - `.env.example` - Environment template ## Acceptance Criteria - [ ] All services start with `docker compose up` - [ ] Health checks pass for all services - [ ] Hot reload works for backend and frontend - [ ] Database data persists across restarts - [ ] All services can communicate - [ ] Documented in DEVELOPMENT.md ## Technical Notes - Reference: Issues #17 (Redis), #18 (Celery), #19 (pgvector) - This issue depends on #17, #18, #19 completion ## Dependencies - Blocked by: #17, #18, #19 ## Assignable To devops-engineer agent
cardosofelipe added the blockeddevopsphase-0 labels 2025-12-29 23:49:40 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
agents
Agent orchestration
 architecture
Architectural decisions
 backend
Backend work
 blocked
Blocked by dependency
 database
Database/migrations
 design
UI/UX design work
 devops
DevOps/Infrastructure work
 epic
Epic/parent issue
 frontend
Frontend work
 infrastructure
Infrastructure / DevOps
 mcp
MCP related
 phase-0
Phase 0: Foundation
 phase-1
Phase 1: Core Platform
 phase-2
Phase 2: MCP Integration
 priority:high
High priority
 spike
Architecture spike / research task
No Label blocked devops phase-0
Milestone
No items
No Milestone
Assignees
Clear assignees
cardosofelipe
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cardosofelipe/syndarix#21
Delete Branch "%!s()"

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?