Jon
Domain no longer accessible on auto-deploy
Unfortunately this didn't turn out to be a long term solution, it's still bugging out. Is there something else I need to add to my config to ensure it can restart and auto-assign whatever black magic is happening in the background when I assign a domain?
3 replies
Domain no longer accessible on auto-deploy
For anyone who might stumble across this later, I fixed the issue by manually adding the appropriate labels in my docker-compose.yml:
labels:
- "traefik.enable=true"
- "traefik.docker.network=dokploy-network"
# HTTP → redirect to HTTPS
- "traefik.http.routers.fchq-api-web.entrypoints=web"
- "traefik.http.routers.fchq-api-web.rule=Host(
api.fchq.io
)"
- "traefik.http.routers.fchq-api-web.middlewares=redirect-to-https@file"
# HTTPS
- "traefik.http.routers.fchq-api-websecure.entrypoints=websecure"
- "traefik.http.routers.fchq-api-websecure.rule=Host(prodapi.fchq.io
)"
- "traefik.http.routers.fchq-api-websecure.tls.certresolver=letsencrypt"
# point Traefik at your internal port
- "traefik.http.services.fchq-api-web.loadbalancer.server.port=3003"
- "traefik.http.services.fchq-api-websecure.loadbalancer.server.port=3003"3 replies
How edit shm size in postgres db?
Has this issue been addressed yet? seems like it would be worthwhile to allow updating the shm size of dokploy containers.
For context, I have a dokploy service installed, 'timescale/timescaledb:2.13.0-pg15' and when accessing the db, I'm getting this:
I can't see any way, other than pulling this out of dokploy, to modify the shared memory size to allow this to work...
13 replies