| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
supports it.
|
|
|
|
|
|
| |
The output from `rails help` actually leaves an empty space when
printing the command lists. This commit adapts this guide to have the
same format.
|
| |
|
|
|
|
|
|
|
|
|
| |
The name of the minitest library is spelled that way: regular font, and
lowercase. Lowercase is used even at the beginning of sentences, see
http://docs.seattlerb.org/minitest/
I double-checked this with @zenspider too (thanks!).
|
|\
| |
| |
| |
| | |
albertoalmagro/albertoalmagro/prefer-rails-command-over-bin-rails
Prefer rails command over bin/rails
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit integrates most used previously rake commands into the
above outer list. Ordering is based on their individual predicted
frequency of use.
Separation between bin/rails tasks is also removed to display all
commands at the same level.
It also removes references to rake and tasks and substitutes them
for 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.
|
|\
| |
| | |
Adds `Rails::Command::NotesCommand` and makes `rake notes` use it under the hood
|
| |
| |
| |
| |
| |
| | |
* Get rid of references to rake notes in the documentation
* Get rid of references to environement variables used in SourceAnnotationExtractor
* Updates the command line guide to reflect the new rails notes API
|
|/
|
|
| |
[Jon Moss & Xavier Noria]
|
|
|
|
|
|
|
| |
[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) "
|
|
|
|
|
|
| |
Skipping over 2.4.0 to sidestep the `"symbol_from_string".to_sym.dup` bug.
References #32028
|
| |
|
|
|
|
|
| |
Passing the environment's name as a regular argument is deprecated
in 48b249927375465a7102acc71c2dfb8d49af8309.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
If system test fails, it creates screenshot under `tmp/screenshots`.
https://github.com/rails/rails/blob/34fe2a4fc778d18b7fe6bdf3629c1481bee789b9/actionpack/lib/action_dispatch/system_testing/test_helpers/screenshot_helper.rb#L45
But currently, screenshot files is not cleared by `tmp:clear` task.
This patch make clears screenshot files with `tmp:clear` task as well
as other tmp files.
|
|
|
|
|
|
| |
Taken from `bin/rails about` run on a v5.1.0.rc1 application.
[ci skip]
|
|
|
|
|
|
|
| |
RC1 is out, `5-1-stable` has been created, figured it was time to start
updating this stuff :)
[ci skip]
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
guides [ci skip]
- Followup of #25692.
|
|/
|
|
|
|
| |
The most complete list of field types appears in the `SchemaStatements` docs rather than the `TableDefinition` docs.
The change to link to `SchemaStatements` means that the explanation for the `index` parameter is no longer available on the linked-to page. A brief explanation of the `index` parameter is added directly in the guide to make up for this.
|
|
|
|
|
|
|
| |
`ActiveRecord::QueryCache` middlewares were removed with `Executor` addition on d3c9d808e3e242155a44fd2a89ef272cfade8fe8
Removes traces and reference of these from all places.
[ci skip]
|
|
|
|
|
|
|
| |
guides [ci skip]
Guides should be updated because ActionDispatch::LoadInterlock was replaced with
ActionDispatch::Executor at #23807.
|
| |
|
| |
|
| |
|
|
|
|
| |
Follow up to #23434
|
|\
| |
| | |
Update middleware docs regarding ActionDispatch::LoadInterlock [ci skip]
|
| | |
|
| |
| |
| |
| | |
use bin/rails instead of rake [ci skip]
|
|\ \
| | |
| | | |
[ci skip] update guide for Puma web server instead of Webrick
|
| | |
| | |
| | | |
Rails 5.0 default server puma web server. following commit - https://github.com/rails/rails/commit/ae48ea69
|
|/ /
| |
| |
| |
| |
| |
| | |
- 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]
|
|/
|
|
|
|
|
|
| |
- Avoided truncating all files if no ENV['LOGS'] specified
- Updated task to accept LOGS=all for truncating all files from log/ i.e. log/*log
- If no LOGS specified will truncates standard environment log files i.e. 'development,test,production'
- CHANGELOG & guide update added
- bin/setup test cases fixed
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
|\
| |
| | |
Upgrade to Ruby 2.2.2
|