Supporting compression on volume backups
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
To Reproduce
it would be helpful to gzip compress volume backs when used via https://docs.dokploy.com/docs/core/volume-backups or have an option to do so. Especially for use-cases like sqlite where the backup sizes will greatly reduce storage.
Current vs. Expected behavior
volume creates only create a tar file - application/x-tar - but a .tar.gz would better utilise storage space on s3
Provide environment information
Version: v0.26.6
Ubuntu
Which area(s) are affected? (Select all that apply)
Application, Docker
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
No response
Will you send a PR to fix it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the volume-backup flow described in the Dokploy documentation and inspect where volume creates produce the current application/x-tar archive. Compare the existing tar output with the requested .tar.gz behavior and verify that compressed backups are stored correctly on S3 while preserving the current backup workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, sqlite
- Domain
- cloud, databases, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100