Normally, all of the settings would be set on `Attachment`, and they
were `deep_merge`d fine. However, if you set the global

    config.paperclip_defaults = { :validate_media_type => false }

then the `HasAttachedFile` class wouldn't pick up on it, because it only
uses things that are defined in the class. This change makes it so that
the default options are merged in to the ones that `HasAttachedFile`
uses when it sets up the attachment.

Fixes #1857

Present methods in roughly the same order as they are referenced,
to make it more graceful to read without jumping back and forth.

In other parts of the codebase, "filename" refers to the part after the
directory path it is contained in. e.g. `original_filename` in
attachment.rb.

This makes this file easier to read by conveying the range of arguments
ContentTypeDetector.new accepts.

Updated the `build missing styles` Capistrano task

Deprecation Warnings:

```
`failure_message_for_should` is deprecated. Use `failure_message` instead. Called from /Users/mugi/git/paperclip/spec/support/matchers/have_column.rb:11:in `block in <top (required)>'.
```

Prioritize MimeMagic over the `file` binary for content type detection
when it finds a match. Fall back to `file` if MimeMagic can't match
anything.

`file` incorrectly detects Open Office XML files (e.g., xlsx, docx) as
zip since they're implemented as zipped archives of xml files. MimeMagic
detects them properly.

[houndci](https://houndci.com) was try to add it because I thought set of tools that can be found in the local environment is want I 'm handy when you pull request

    bundle exec rake cucumber

to log

```
Capybara::RSpecMatchers::HaveText implements a legacy RSpec matcher
protocol. For the current protocol you should expose the failure messages
via the failure_message and failure_message_when_negated methods.
```

See
https://github.com/jnicklas/capybara/issues/1254
https://github.com/jnicklas/capybara/pull/1219

Use Updated Version of `aws-sdk` in Docs [ci skip]

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.

* 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.

Rescue only `NotIdentifiedByImageMagickError` in
`Attachment#post_process_style`. Other errors should bubble up, because
they are meaningless for the end-user, but important for the programmer.

Fixes #1352.

Remove RubyForge project name from gemspec

http://docs.travis-ci.com/user/workers/container-based-infrastructure/

With Container based CI, public projects can cache the results of bundle
install

It's useless because there is the same conditional in https://github.com/thoughtbot/paperclip/blob/master/lib/paperclip/railtie.rb#L25, and if ActiveRecord is not defined, Glue will not run.

Updated gemspec to fix issue #1729

Updated gemspec to require aws-sdk gem ~> 1.6

* Move the thanks to contributors to the contributing section
* Introduce the new "About thoughtbot" section.

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.