1. 23 Mar, 2016 1 commit
    • Add fog_options to configuration to be passed to fog #create · 65ef0d34
      We found that uploading large files to S3 would result in a socket error
      ("connection reset by peer") occasionally and lately much more
      consistently. In researching this I saw that many people got this error
      when uploading too large of a file without multipart chunking. I would
      have assumed fog did this automatically but the default chunk size may
      be too high. In order to address this I wanted to drop the chunk size to
      100MB.
      
      Rather than hard-code this I opted to expose a `fog_option`
      configuration option that lets me pass any additional options I want to
      the fog's `#create` call. This is similar to the `fog_attributes` option
      implemented in CarrierWave which [addresses the same
      problem](http://stackoverflow.com/a/11867978/201911).
      
      We've been running this now for a week in production and it seems to
      resolve the issue.
      
      https://github.com/thoughtbot/paperclip/pull/2135
      Jeremy Wadsack committed
  2. 12 Mar, 2016 1 commit
  3. 26 Feb, 2016 1 commit
  4. 26 Jan, 2016 2 commits
  5. 16 Jan, 2016 1 commit
  6. 15 Jan, 2016 1 commit
    • Skip calculating fingerprint when it is not used · 53a386c5
      The MD5 sum of an attachment is only necessary if the model has a corresponding
      _fingerprint column. If this column is absent, there is no need to calculate the
      MD5, which can be an expensive operation for large files.
      
      Accomplish this by deferring the fingerprint calculation using a block. If the
      _fingerprint column is absent, the block is never called, and the calculation
      is avoided.
      Matt Brictson committed
  7. 14 Jan, 2016 1 commit
  8. 13 Jan, 2016 2 commits
    • Modify the Gemfile for testing with mime-types 3 · f0bd25ad
      -   Also modify the appraisals to be more flexibly specified.
      -   The specs are '>= 1.16' and '< 4.0' because the major versions of
          mime-types have steadily restricted the supported versions of Ruby at a
          different rate than Rails. The Appraisal for Rails 5 can be specified as
          either '>= 2.0, '< 4.0' or '~> 3.0' depending on how other gems restrict
          mime-types versions.
      
          -   mime-types 1.x supports any version of Ruby, but no longer receives any
              updates (it hit EOL on 27 October 2015).
          -   mime-types 2.x supports Ruby >= 1.9.2, but will only receive security
              and data updates until 21 November 2017.
          -   mime-types 3.x supports Ruby >= 2.0 and is the active development
              version of mime-types.
      
      -   The APIs that paperclip uses are compatible between all three versions of
          mime-types.
      Austin Ziegler committed
    • Merge pull request #2085 from jaredbeck/allow_mimemagic.0.3.1 · 06d5efc8
      Relax mimemagic version constraint to ~> 0.3.0
      Jon Moss committed
  9. 04 Jan, 2016 1 commit
  10. 03 Jan, 2016 4 commits
  11. 02 Jan, 2016 2 commits
  12. 23 Dec, 2015 1 commit
  13. 22 Dec, 2015 4 commits
  14. 02 Dec, 2015 5 commits
  15. 25 Nov, 2015 1 commit
  16. 22 Nov, 2015 1 commit
  17. 21 Nov, 2015 1 commit
  18. 20 Nov, 2015 1 commit
  19. 19 Nov, 2015 4 commits
  20. 18 Nov, 2015 1 commit
  21. 17 Nov, 2015 3 commits
  22. 16 Nov, 2015 1 commit