-
Notifications
You must be signed in to change notification settings - Fork 0
Compose Architecture
Docker Compose is the local production-shape topology. Standard projects receive it only when Docker is selected; Praxis Pro always includes pro.compose after stack/capability modules.
flowchart TD
User[developer/operator] --> Compose
Compose --> API
Compose --> DB[(PostgreSQL or selected DB)]
Compose --> Cache[(Redis/Memcached when selected)]
Compose --> Worker[worker when selected]
Compose --> Scheduler[scheduler when selected]
Compose --> Services[search/storage/telemetry when selected]
Health[health conditions] --> API
Health --> Worker
deployment.docker selects root/frontend/backend artifacts by project type and patches selected database/cache services and internal URLs. The backend still performs readiness checks and graceful cleanup.
pro.compose starts from a Django or Go base. Capability overlays add only required services and commands: Redis before jobs, workers before scheduled/email work, and selected search/storage/telemetry services. Health-conditioned dependencies model readiness; depends_on alone is not treated as application readiness.
- Compose owns containers, networks, volumes, environment injection, restart policy, and dependency conditions.
- Application processes own schema/migration semantics, request behavior, client lifecycle, and graceful shutdown.
- Kubernetes is a separate deployment model, not generated from Compose at runtime.
- Terraform provisions cloud foundations and managed services; it does not invoke Compose.
Add a service only when a resolved selection requires it. Give stateful dependencies health checks and persistent volumes where appropriate. Use internal service names in container URLs and documented developer values in .env.example. Keep secrets external to committed Compose files.
This Wiki is generated from the repository's versioned docs/ source. Update and review the source files; do not rely on hand edits to generated Wiki pages.
- Core-Internals
- Architecture
- Repository-Map
- Code-Architecture
- Generation-Pipeline
- Manifest-System
- UI-Templates
- Testing
- Agent-Guide
- Wiki-Publishing
- Template-Architecture
- Standard-Projects
- Standard-Frontend-Architecture
- Express-Architecture
- Fullstack-Architecture
- Praxis-Pro
- Django-Architecture
- Gin-Architecture
- Capability-Architecture
- Compose-Architecture
- Kubernetes-Architecture
- Terraform-Architecture
- Extending-Generated-Projects
- Generated-Backends