DUP-297: Add drush backup cleanup cron#75
Open
martinstadelmann wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue
Drush uses
/app/drush-backupsfor temporary storage of Drupal database backups (as well as some other ephemeral files). However in some edge cases, like an aborteddrush sqs:syncit is possible that the file(s) are not cleaned up properly and remain in the folder. We could move the drush backups folder into/tmpusing the drush config, however the temporary directory's storage limit (8GB on Upsun) differs from the app's and the/tmpfolder might not be cleaned up quickly.Tasks
.platform.app.yamlconfigurations