Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Don’t exclude some file in lib from rubocop | Douwe Maan | 2017-02-23 | 1 | -4/+4 |
| | |||||
* | # This is a combination of 2 commits. | Drew Blessing | 2017-02-21 | 1 | -1/+16 |
| | | | | | | | | | | | | | | | | | | # This is the 1st commit message: Add `copy` backup strategy to combat file changed errors The backup Rake task used to stream data directly from the live data directory into the backup. Under many circumstances this worked OK. However, really active instances would experience a 'file changed as we read it' error - especially with data like the registry. This now copies the data first, then compresses it. It will take a bit more disk space while the backup is in progress, but it's a necessary thing. # The commit message #2 will be skipped: # Add env var | ||||
* | Use `File::exist?` instead of `File::exists?` | bogdanvlviv | 2016-08-11 | 1 | -1/+1 |
| | | | | Since version ruby-2.2.0, method `File::exists?` is deprecated. | ||||
* | Do no rely on basename of builds, uploadsbackup-improvements | Jacob Vosmaer | 2015-10-16 | 1 | -4/+5 |
| | |||||
* | Remove unused variable | Jacob Vosmaer | 2015-10-06 | 1 | -3/+2 |
| | |||||
* | Remove old "files" tarball explicitly | Jacob Vosmaer | 2015-10-06 | 1 | -0/+1 |
| | |||||
* | Use tar for intermediate backup storage | Jacob Vosmaer | 2015-10-06 | 1 | -0/+39 |
During the backup we create an intermediate copy of two directories: builds and uploads. Instead of creating many small files with 'cp -r', we now use tar (and fast gzip) to create single intermediate files. This saves on disk IO and disk space while creating a backup. |