Skip to content
Snippets Groups Projects
Select Git revision
  • ag-test
  • rs-test
  • master default protected
  • test-me-pa
  • mksionek-master-patch-52381
  • new-branch-10
  • test-conflicts
  • test-suggestions
  • alejandro-test
  • patch-25
  • winh-test-image-doscussion
  • stg-lfs-image-test-2
  • stg-lfs-image-test
  • test42016
  • issue_42016
  • issue-32709
  • add-codeowners
  • ClemMakesApps-master-patch-62759
  • bvl-staging-test
  • bvl-merge-base-api
  • v9.2.0-rc6 protected
  • v9.2.0-rc5 protected
  • v9.2.0-rc4 protected
  • v9.2.0-rc3 protected
  • v9.1.4 protected
  • v9.2.0-rc2 protected
  • v9.2.0-rc1 protected
  • v9.1.3 protected
  • v8.17.6 protected
  • v9.0.7 protected
  • v9.1.2 protected
  • v9.1.1 protected
  • v9.2.0.pre protected
  • v9.1.0 protected
  • v9.1.0-rc7 protected
  • v9.1.0-rc6 protected
  • v9.0.6 protected
  • v9.1.0-rc5 protected
  • v9.1.0-rc4 protected
  • v9.1.0-rc3 protected
40 results

files.rb

  • Drew Blessing's avatar
    d6584c94
    # This is a combination of 2 commits. · d6584c94
    Drew Blessing authored
    # 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
    d6584c94
    History
    # This is a combination of 2 commits.
    Drew Blessing authored
    # 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
Code owners
Assign users and groups as approvers for specific file changes. Learn more.