infra: split deploy into frontend delivery and langfuse projects
This commit is contained in:
17
deploy/README.md
Normal file
17
deploy/README.md
Normal file
@@ -0,0 +1,17 @@
|
||||
# Deployment Split
|
||||
|
||||
This repository now includes independent compose files per project:
|
||||
|
||||
- `deploy/frontend/docker-compose.yml` - Nuxt app (UI + Nitro API/GraphQL + Prisma access)
|
||||
- `deploy/delivery/docker-compose.yml` - delivery worker only
|
||||
- `deploy/langfuse/docker-compose.yml` - Langfuse + ClickHouse/Redis/Postgres/MinIO
|
||||
|
||||
Use separate Dokploy projects so each stack can be redeployed independently.
|
||||
|
||||
## Recommended Dokploy mapping
|
||||
|
||||
1. Frontend project -> `deploy/frontend/docker-compose.yml`
|
||||
2. Delivery project -> `deploy/delivery/docker-compose.yml`
|
||||
3. Langfuse project -> `deploy/langfuse/docker-compose.yml`
|
||||
|
||||
`deploy-map.toml` contains the same paths in `[services]`.
|
||||
Reference in New Issue
Block a user