Skip to content

P
paperclip
Switch branch/tag
  1. 24 Apr, 2015 1 commit
  3. 23 Apr, 2015 1 commit
    • Use Updated Version of `aws-sdk` in Docs [ci skip] · c7066936 
      The `aws-sdk` development dependency was updated to `~> 1.6` in #1816
to resolve issues with the creation of 0-byte files on S3 (see #1729).
However, there is no runtime dependency on `aws-sdk`, and the
documentation still suggests that users install an earlier version of
`aws-sdk` that produces the problems in the referenced issue.

This commit updates the docs to recommend the use of `aws-sdk` `~> 1.6`
with Paperclip.
      Robert Eshleman committed
  5. 17 Apr, 2015 3 commits
  7. 15 Apr, 2015 1 commit
    • Fix for Errno::ENAMETOOLONG in Thumbnails · c81970d9 
      * Uses Paperclip's Tempfile instead of Ruby's in Thumbnail
* Also includes a test for TempfileFactory to be sure it does not revert to similar behavior
* In the tests, give the OS some wiggle room in the Tempfile name to ensure the error does not occur before we are ready for it. The wiggle room is needed because the randomized part of the name has a variable number of characters.
      Sammy Larbi committed
  9. 25 Mar, 2015 2 commits
  11. 24 Mar, 2015 2 commits
  13. 21 Mar, 2015 1 commit
  15. 13 Mar, 2015 4 commits
  17. 12 Mar, 2015 1 commit
  19. 13 Feb, 2015 1 commit
    • Use Travis container infrastructure · 97c78efd 
      The container infrastructure (beta) has many advantages:
* More memory
* More CPU
* builds start much faster.
* builds run much faster (usually)

However, `sudo` cannot be used when running in this environment (which
is enabled with the `sudo: false` configuration.
      Derek Prior committed
  21. 06 Feb, 2015 8 commits
  23. 03 Feb, 2015 1 commit
  25. 06 Jan, 2015 1 commit
    • Don't assume we have Rails.env if we have Rails · c46b40b9 
      As referenced in #1739

Just because the `Rails` constant is defined, it doesn't mean we're
actually in a Rails app. Since there are people who use Paperclip
outside of Rails, and there's no reason we shouldn't be able to run in
those situations. This commit checks for `Rails.env` instead of just
checking for `Rails` and assuming `Rails.env` works.
      Jon Yurek committed
  27. 23 Dec, 2014 2 commits
  29. 19 Dec, 2014 2 commits
  31. 12 Dec, 2014 3 commits
  33. 09 Dec, 2014 2 commits
  35. 08 Dec, 2014 3 commits
  37. 05 Dec, 2014 1 commit
    • Fog upgraded how expiring_urls are made · 3398282e 
      Turns out that between fog 1.22.0 and fog 1.25.0, there was a change to
how fog builds S3 expiring URLs. This changes to test to be the common
point between the two versions. All we need to do here is make sure that
the expiring URL is being constructed.

In the process, this also updates all the appraisal-generated
Gemfiles.

Also, in the process, this meant I had to take away the builder version
restriction. This was put in so that `bundle`ing wouldn't take forever,
but I'm unsire whether this needed to happen with this version or if
builder just needed to be separate from the Gemfile. I'm commimtting
this and asking the people who reported the problem. If you don't see a
revet commit, everything was fine.
      Jon Yurek committed