allucanget/ai.allucanget.biz
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add docker-compose.coolify.yml for backend and frontend services; update deployment documentation for Coolify integration

Browse Source 
Co-authored-by: Copilot <copilot@github.com>
This commit is contained in:
zwitschi
2026-04-28 11:18:00 +02:00
parent fe41a8cbee
commit 87efca00df
3 changed files with 133 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/7-deployment-view.md
+5 -5
View File
@@ -96,11 +96,11 @@ All services are containerized and orchestrated with `docker compose`:
If using Coolify instead of Docker Compose:
1. **Backend Service**: Nixpacks build with base directory `/backend`, port 12000
2. **Frontend Service**: Nixpacks build with base directory `/frontend`, port 12001
3. **Reverse Proxy**: Coolify's built-in proxy or custom Nginx config
4. **Data Persistence**: Volume mount at `/app/data` for DuckDB
1. **Recommended Path**: Deploy `docker-compose.coolify.yml` as one Coolify Docker Compose resource
2. **Public Entry Point**: Route domain to `nginx` service on port 80; backend and frontend stay internal
3. **Data Persistence**: Named volume keeps DuckDB data at `/app/data`
4. **Fallback Path**: Use separate Nixpacks services only when one-stack Compose deploy is not suitable
**Note**: Both services must be on the same Coolify server or cluster for service-to-service communication via `http://localhost:12000` or service DNS names (depending on Coolify's networking setup).
**Note**: In Compose-based Coolify deployment, frontend reaches backend through Docker DNS at `http://backend:12000`. In Nixpacks-based deployment, use Coolify internal networking or colocate both services.
**See**: [Coolify Deployment Guide](./deployment/coolify.md) for detailed instructions.