Skip to content

P
paperclip
Switch branch/tag
  1. 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
  3. 25 Mar, 2015 2 commits
  5. 24 Mar, 2015 2 commits
  7. 21 Mar, 2015 1 commit
  9. 13 Mar, 2015 4 commits
  11. 12 Mar, 2015 1 commit
  13. 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
  15. 06 Feb, 2015 8 commits
  17. 03 Feb, 2015 1 commit
  19. 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
  21. 23 Dec, 2014 2 commits
  23. 19 Dec, 2014 2 commits
  25. 12 Dec, 2014 3 commits
  27. 09 Dec, 2014 2 commits
  29. 08 Dec, 2014 3 commits
  31. 05 Dec, 2014 6 commits
    • 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
    • Revert "Fast to slowly spec" · d02b2fcd 
      This reverts commit ae3ec237.
      Jon Yurek committed
    • Revert "remove whitespace, not main gemspec" · 3601cc6b 
      This reverts commit 8d70c198.
      Jon Yurek committed
    • Revert "Fog upgraded how expiring_urls are made" · 68d777fb 
      This reverts commit 8e0eb4ce.
      Jon Yurek committed
    • Fog upgraded how expiring_urls are made · 8e0eb4ce 
      During the fixing of the previous commit, the tests broken. 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
    • remove whitespace, not main gemspec · 8d70c198
      soramugi committed