Blogs/blogs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Attach Dokploy compose service to proxy network
Some checks are pending
Build / build (push) Waiting to run
Details

Browse source
This commit is contained in:
Neeldhara Misra 2026-06-13 20:03:47 +02:00
parent 80c51bdfea
commit b3cd8a8914
2 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
DEPLOYMENT.md
View file

@ -72,6 +72,8 @@ Use the Docker Compose deployment path.
The container builds all seven sites with `npm run build`. Nginx reads the `Host` header and serves the matching directory using `deploy/nginx.conf`.
The Compose app attaches to Dokploy's external `dokploy-network` so Dokploy's proxy can reach the container. If your Dokploy installation uses a different proxy network name, update `docker-compose.yml`.
## DNS
Point these DNS records at the Dokploy host:
@ -100,3 +102,13 @@ curl -I https://puzzles.neeldhara.blog/rss.xml
```
Expected result: `200 OK` for each.
## Bad Gateway Checklist
If Dokploy shows `Bad Gateway`:
1. Confirm the app deployment finished successfully and the `blogs` container is running.
2. In the domain settings, make sure each domain points to service `blogs` and container port `80`.
3. Confirm the service is attached to `dokploy-network`.
4. Check the container logs. Nginx should stay in the foreground; if it exits, the logs should show the config error.
5. Redeploy after any Compose change so Dokploy recreates the container/network attachment.