Skip to content

🔧 fix: use named volume for backups in coolify deployment #137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
thies2005 merged 1 commit into from
Mar 18, 2026
Merged

🔧 fix: use named volume for backups in coolify deployment #137

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions Web/docker-compose.coolify.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ services:
- runflow-network
- coolify
volumes:
- ./backups:/app/backups
- backups:/app/backups
healthcheck:
test:
[
Expand Down Expand Up @@ -90,7 +90,7 @@ services:
command: sh -c "mkdir -p /backups && chown -R 1001:1001 /backups && chmod -R 775 /backups"
restart: "no"
volumes:
- ./backups:/backups
- backups:/backups
networks:
- runflow-network
logging:
Expand Down Expand Up @@ -170,7 +170,7 @@ services:
- BACKUP_KEEP_MONTHS=6
- HEALTHCHECK_PORT=8080
volumes:
- ./backups:/backups
- backups:/backups
depends_on:
db:
condition: service_healthy
Expand Down Expand Up @@ -236,3 +236,4 @@ networks:

volumes:
postgres_data:
backups: