[Carlos Antonio da Silva & Santiago Pastorino]

[Carlos Antonio da Silva & Santiago Pastorino]

[Carlos Antonio da Silva & Santiago Pastorino]

[Carlos Antonio da Silva & Santiago Pastorino]

Change application controller template accordingly, to inherit from
ActionController::HTTP and not generate protect_from_forgery call.

[Carlos Antonio da Silva & Santiago Pastorino]

uses PATCH for the forms of persisted records, and routes PATCH and PUT to the update action of resources

PATCH is the correct HTML verb to map to the #update action. The
semantics for PATCH allows for partial updates, whereas PUT requires a
complete replacement.

Changes:
* adds config.default_method_for_update you can set to :patch
* optionally use PATCH instead of PUT in resource routes and forms
* adds the #patch verb to routes to detect PATCH requests
* adds #patch? to Request
* changes documentation and comments to indicate support for PATCH

This change maintains complete backwards compatibility by keeping :put
as the default for config.default_method_for_update.

We still looking for a best presentation for tests output.

Fix CI and rename 1 misleading test case.

assets.cache_store now defaults to filesystem. You will want to share tmp/assets_cache between deploys.

This makes "sprockets/railtie" explicit. This means that sprockets will
be loaded when you require "rails/all". If you are not using requiring
"rails/all", you need to manually load it with all other framework
railties.

In order to be complete, this commit also adds --skip-sprockets to
the rails generator.

sqlite3 based app