Fix No route matches GET "/assets/application.css"

We use Rails' asset pipeline's `config.assets.digest = true` setting to
add a hash to the name of the application.css file. This means it isn't
available using this path.
Add a --skip-git option

The only reason suspenders should not be run against an existing
directory is because it initializes a git repo. Allow for that to be
skipped.

Suspenders isn't ready to handle upgrading an existing app, but it can
now handle this situation:

    % git checkout --orphan rewrite-the-spike
    % cd ..
    % suspenders create my-project --skip-git true
Comment before action_on_unpermitted_parameters

The `config/environments/development.rb` file has comments before each
of its settings, but a comment is missing when we insert
`action_on_unpermitted_parameters`. The lack of symmetry made me sad,
and the fact that we may hand the project off to another dev team makes
me think we should document it.

The `#configure_environment` method was inserting spaces for us, but
those spaces were throwing the formatting off for multi-line insertions.
Fall back to `#inject_into_file` instead.
Disable jQuery animations in tests
Set Heroku remotes without using concat_file

* Fix https://github.com/thoughtbot/suspenders/issues/227
* Fix space between git host and git repo name.
Enable Rack::Deflater compression of controller-generated responses
Bump to 1.6.0
Fix NEWS.md: Rack::Deflater, not Rack::Timeout
Keep db/schema.rb in version control

* Remove db/schema.rb from generated .gitignore
* Checking in db/schema.rb is recommended by Rails core
* An existing db/schema.rb is required for rake db:setup
* Defer database creation until all migrations are generated
* Run migrations to ensure db/schema.rb is created with new apps
Fail bin/setup if subcommands fail

* Fail tests if bin/setup doesn't work
* Allow chaining bin/setup with &&
* Don't attempt subsequent setup steps if prerequisites fail
Move secret key out of version control

* Use environment variables
* Set dummy value for development
* Automatically generate values for new Heroku apps

More information:
http://blog.codeclimate.com/blog/2013/03/27/rails-insecure-defaults/
Generate a `.ruby-version` file in new applications

* Ensure everybody is using the same version of Ruby, include patchlevel
Add placeholder for feature spec helpers

* Create empty spec/features, spec/support/features
* Create .keep files to force Git to track directories
* Create and include empty Features module in spec_helper.rb

More information:
https://github.com/thoughtbot/guides/blob/master/style/README.md#acceptance-tests
Improve generated README

* Include the app name so it doesn't look like the README for suspenders
* Include getting started instructions based on the [Protocol]

[Protocol]: http://github.com/thoughtbot/guides/blob/master/protocol
Bump to 1.7.0 and document changes since 1.6.0

* Update version.rb
* Update README.md
* Update NEWS.md
Reduce ActiveRecord connection pool from 5 to 2

We're lowering the ActiveRecord connection pool maximum from the default
of 5. A basic Rails app with 2 Heroku web dynos that each have 3 Unicorn
workers, plus two Delayed Job background workers could have up to 40
database connections if ActiveRecord or our code is causing hung
connections.

While the Rails 4 reaper will close dead connections every 10 seconds,
limiting the total to 1 per process (8 in this case), we still maintain
some Rails 3 apps. Also, while it is likely that over time our
application may have a few connections that hang, if something in our
code is causing hung connections, the reaper will not be a permanent fix
to the problem.

Depending on the pricing plan, production Heroku Postgres databases have
a maximum of 60 to 500 connections. That sounds like a lot, but it's
likely that before the max is hit, we'll run into some other resource
contention like CPU, IO throughput, or memory. Database throughput will
hit a local max and then degrade as number of connections increase.

2 is a good default as opposed to 1 because New Relic's auto-EXPLAIN
feature also adds 1 connection per Unicorn (or background job).

https://devcenter.heroku.com/articles/concurrency-and-database-connections
Add dotenv-rails to always load .env files

* Sets up ENV for rake tasks, tests environment
* Eliminate defaults just for tests

https://trello.com/c/TGRehrWA/205-dotenv-rails
Restrict dotenv-rails to development, test

* Prevents accidental dev configuration in production

https://github.com/thoughtbot/suspenders/pull/248
Add spring

It's good stuff, and Rails 4.1 will include Spring by default. We may as
well get on this train early.

https://github.com/rails/rails/commit/6f72a6b53afda51a73af69194ed0060ea5048fa9
Remove dead code

* Removes builder calls to non-existent methods
* Remove clearance generator, as clearance isn't in the Gemfile
* Remove unused copy_libraries method