| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| |
| |
| | |
albertoalmagro/albertoalmagro/prefer-rails-command-over-bin-rails
Prefer rails command over bin/rails
|
| |
| |
| |
| | |
This commit substitutes references to rails/rake task for rails command
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As discussed in #33203 rails command already looks for, and runs,
bin/rails if it is present.
We were mixing recommendations within guides and USAGE guidelines,
in some files we recommended using rails, in others bin/rails and
in some cases we even had both options mixed together.
|
|/
|
|
|
| |
http links will be redirected to the https version, but still better to
just directly link to the https version.
|
|
|
|
|
|
|
| |
[ci skip] A regular expression was used to find a lot of missing Oxford
commas and add them. The regular expression was as follows.
", ([a-zA-Z0-9.\`:'\"]+ ){1,6}(or|and) "
|
| |
|
|
|
|
|
| |
Document in the guides the new middleware added in #31162
[ci skip]
|
|\
| |
| | |
Update Rails on Rack guide [ci skip]
|
| | |
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
| |
* Adjust middlewares list to match current defaults
* application.routes runs on application object, not Rails
* Add explanation of Sprockets::Rails::QuietAssets
|
|
|
|
|
|
|
| |
We mention the "resources" section of the guide in the next paragraph,
and the link is listed there. IMHO we shouldn't list it twice.
[ci skip]
|
|
|
|
| |
[ci skip]
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
the same.
https://github.com/rails/rails/commit/23b6a9c0fcb8992e18450d6fe0680bf09685b7db
[ci skip]
|
|
|
|
|
|
|
| |
`ActiveRecord::QueryCache` middlewares were removed with `Executor` addition on d3c9d808e3e242155a44fd2a89ef272cfade8fe8
Removes traces and reference of these from all places.
[ci skip]
|
|
|
|
|
|
| |
changed quite a bit after Executor middleware addition.
[ci skip]
|
|
|
|
|
|
|
| |
guides [ci skip]
Guides should be updated because ActionDispatch::LoadInterlock was replaced with
ActionDispatch::Executor at #23807.
|
| |
|
|\
| |
| | |
Update middleware docs regarding ActionDispatch::LoadInterlock [ci skip]
|
| | |
|
|/
|
|
|
|
|
| |
- Only ones left are from the upgrading guide, and command line guide explicit section about rake
Follow up of https://github.com/rails/rails/pull/23119
[ci skip]
|
|
|
|
|
|
|
|
| |
Should use `public_file_server.enabled` instead.
Clarified that static files will be served from the public directory, where it made sense.
Also removed occurrence of the deprecated `static_cache_control`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 37423e4ff883ad5584bab983aceb4b2b759a1fd8.
Jeremy is right that we shouldn't remove this. The fact is that many
engines are depending on this middleware to be in the default stack.
This ties our hands and forces us to keep the middleware in the stack so
that engines will work. To be extremely clear, I think this is another
smell of "the rack stack" that we have in place. When manipulating
middleware, we should have meaningful names for places in the req / res
lifecycle **not** have engines depend on a particular constant be in a
particular place in the stack. This is a weakness of the API that we
have to figure out a way to address before removing the constant.
As far as timing attacks are concerned, we can reduce the granularity
such that it isn't useful information for hackers, but is still useful
for developers.
|
|\
| |
| | |
use class to specify the middleware [ci skip]
|
| |
| |
| |
| | |
using string for middleware class names is deprecated in 83b767cef90abfc4c2ee9f4b451b0215501fae9a
|
|/
|
|
|
|
|
|
|
|
|
|
| |
The runtime header is a potential target for timing attacks since it
returns the amount of time spent on the server (eliminating network
speed). Total time is also not accurate for streaming responses.
The middleware can be added back via:
```ruby
config.middleware.ues ::Rack::Runtime
```
|
|
|
|
|
| |
This can still be added to the middleware stack, but is really not
necessary. I'll follow up with a commit that deprecates the constant
|
|
|
|
|
|
|
|
|
|
|
| |
As of 56903585, the Rack::ContentLength middleware isn't included by
default anymore.
The only remaining middleware is Rack::Lock ; since it's only included
when using WEBrick, it's certainly not worth documenting it in the
guides.
[ci skip]
|
|\
| |
| |
| |
| | |
Conflicts:
guides/source/configuring.md
|
| |
| |
| | |
[ci skip]
|
|/
|
|
| |
Rails::Rack::Debugger was removed in 93559da4826546d07014f8cfa399b64b4a143127
|
| |
|
|
|
|
| |
- Changed `IN` to `ON` in all note sentences in guides.
|
|
|
|
|
| |
bebugger doesn't work with Ruby 2.2 so we don't need to support it
anymore
|
|
|
|
| |
References #18148.
|
|
|
|
|
|
| |
Allow static asset serving from env variable (enhanced!)
Conflicts:
railties/CHANGELOG.md
|
| |
|
|
|
|
| |
cc #17719
|
|
|
|
|
| |
ActionDispatch::Callbacks dose not run the prepare callbacks,
so change with comment on ActionDispatch::Callbacks.
|
|
|
|
|
|
|
|
|
| |
Add a section in the guide to explain that Rails can't auto-reload
a middleware on code change.
Fix #16806
[ci skip]
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
| |
References to ``AppName::Application` removed in favour of ``Rails.application``
as generated with a new rails 4.1 app.
[ci skip]
|
|
|
| |
[ci skip]
|
|
|
|
| |
[ci skip]
|