Skip to content
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.

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

[REQUEST] Add control over compression to the backup systems #5822

Closed
proimage opened this issue Mar 20, 2020 · 3 comments
Closed

[REQUEST] Add control over compression to the backup systems #5822

proimage opened this issue Mar 20, 2020 · 3 comments
Labels
enhancement improvements to existing features system administration 💼 features related to system administration
Milestone

Comments

@proimage
Copy link

Currently the only way to get the DB backups compressed is to select "Download backup" in the backend (or, obviously, to DIY it). But that doesn't affect the file saved on the server, and with MySQL backups often taking up ~10x more space uncompressed than compressed, it would make a huge difference if the admin could elect to have them stored in compressed format server-side:

image

For the backend, another checkbox would do it:

image

And for the terminal, something like ./craft backup/db-tar or ./craft backup/db-zip, perhaps?

@brandonkelly brandonkelly added enhancement improvements to existing features system administration 💼 features related to system administration labels Mar 20, 2020
@brandonkelly
Copy link
Member

brandonkelly commented Mar 20, 2020

Honestly this probably shouldn’t even be a setting. Craft should probably just be compressing all backups on save.

@brandonkelly brandonkelly added this to the 3.5 milestone Mar 20, 2020
@proimage
Copy link
Author

Works for me. ¯_(ツ)_/¯

@brandonkelly
Copy link
Member

Done for Craft 3.5!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement improvements to existing features system administration 💼 features related to system administration
Projects
None yet
Development

No branches or pull requests

2 participants