| Name |
Last commit
|
Last Update |
|---|---|---|
| cucumber | ||
| features | ||
| gemfiles | ||
| lib | ||
| shoulda_macros | ||
| test | ||
| .gitignore | ||
| .travis.yml | ||
| Appraisals | ||
| CONTRIBUTING.md | ||
| Gemfile | ||
| LICENSE | ||
| NEWS | ||
| README.md | ||
| RUNNING_TESTS.md | ||
| Rakefile | ||
| UPGRADING | ||
| paperclip.gemspec |
When using S3 for storage, their data consistency model makes the current behaviour of Attachment#reprocess! unreliable. Apparently, Amazon can not guarantee that PUT's called after DELETE's is actually executed in that order. Hence, I propose preserving files, when doing a reprocces.
| Name |
Last commit
|
Last Update |
|---|---|---|
| cucumber | Loading commit data... | |
| features | Loading commit data... | |
| gemfiles | Loading commit data... | |
| lib | Loading commit data... | |
| shoulda_macros | Loading commit data... | |
| test | Loading commit data... | |
| .gitignore | Loading commit data... | |
| .travis.yml | Loading commit data... | |
| Appraisals | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| Gemfile | Loading commit data... | |
| LICENSE | Loading commit data... | |
| NEWS | Loading commit data... | |
| README.md | Loading commit data... | |
| RUNNING_TESTS.md | Loading commit data... | |
| Rakefile | Loading commit data... | |
| UPGRADING | Loading commit data... | |
| paperclip.gemspec | Loading commit data... |