| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Create tmp folder if not present
|
| | |/ /
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
All Apps may not have a tmp folder
Update dev.rake
Update dev.rake
Update dev.rake
Update dev.rake
Update dev.rake
Update dev.rake
Update dev.rake
|
|/ / / |
|
|/ /
| |
| |
| |
| | |
Puma 3.0 and up introduced compatibility to read from `config/puma.rb` when booting from the command `$ rails server`https://github.com/puma/puma/pull/856.
|
| |
| |
| |
| |
| | |
- We will remove the initializer for old apps which are migrated to
Rails 5 so that they are not affected by this breaking change.
|
| |
| |
| |
| |
| |
| | |
subdomains
- We will reuse config.ssl_options for setting the HSTS settings.
|
|\ \
| | |
| | | |
Fix README heading according to Markdown conventions
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The first heading in some README's are indicated using a second level
heading (`##`), which in my opinion is of incorrect structure.
Therefore, in this patch I changed the first heading to a first level
heading (`#`) in README's where this incorrect structure occurs.
[ci skip]
|
| | | |
|
| | |
| | |
| | |
| | | |
This also marks Action Cable routes as internal to Rails.
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #23855
|
| | | |
|
|/ /
| |
| |
| |
| | |
coffee-rails is stable now so we don't need to point to the master
branch.
|
|\ \
| | |
| | | |
AppGenerator: Replace 'rake' with 'rails_command'
|
| | |
| | |
| | |
| | |
| | | |
Follows the convention from Rails 5 of invoking tasks on the command-line
with `rails …` rather than `rake …`.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since Rails 5.0 is switching the Rails command line from 'rake …'
to 'rails …', it makes sense to also replace the `rake` method in
the Rails templates API.
Based on feedback from @matthewd and @kaspth, I chose to replace
`rake` with `rails_command`, which is less confusing than
the alternatives `rails` or `command` or `rails_run` and is not
Thor-reserved word like `task`.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a rebased version of #22825.
Closes #22825.
|
| | | |
| | | |
| | | |
| | | | |
environment templates
|
| | | | |
|
| | | | |
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Alternative to #23638 log to STDOUT via env var
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
People who deploy to containers or other places where they might have some sort of a log wrapping service use stdout. With this change new rails apps can be configured to output to STDOUT via setting `RAILS_LOG_TO_STDOUT` to any value. This allows container images or services to set the value for all apps without having to modify configuration for each application. If an app wants to opt out, they can either delete from the env hash, or remove that configuration.
cc/ @rafaelfranca
|
|\ \ \ \
| | | | |
| | | | | |
Add `internal` attribute to routes
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is meant to provide a way for Action Cable, Sprockets, and possibly
other Rack applications to mark themselves as internal, and to exclude
themselves from the routing inspector, and thus `rails routes` / `rake
routes`.
I think this is the only way to have mounted Rack apps be marked as
internal, within AD/Journey. Another option would be to create an array
of regexes for internal apps, and then to iterate over that everytime a
request comes through. Also, I only had the first `add_route` method set
`internal`'s default to false, to avoid littering it all over the
codebase.
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
We should be able to pass options to minitest via TESTOPTS environment
variable
|
| | | |
| | | |
| | | |
| | | | |
Get it? ( ͡° ͜ʖ ͡°)
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | | |
The process of converting `Test` to `String` is already defined in minitest.
I think it is better to use that for the consistency of output content.
ref: https://github.com/seattlerb/minitest/blob/master/lib/minitest/test.rb#L261..L267
|
| | |
| | |
| | |
| | |
| | |
| | | |
If you want to use `EventedFileUpdateChecker`, need to specify `listen` to plugin's gemspec.
However, the default is not specified `listen` to plugin's gemspec,
`EventedFileUpdateChecker` should be disabled.
|
|\ \ \
| |/ /
|/| | |
modify to `error` also abort when specify fail fast option
|
| | | |
|
|/ /
| |
| |
| | |
`app_templates_dir` is unused since dc53fe9.
|
| | |
|
|\ \
| | |
| | | |
generate mailer views in Rails API
|
| | |
| | |
| | |
| | |
| | | |
View files is necessary to send mail, it should be generated even Rails API.
Fixes #23617
|
| | |
| | |
| | |
| | |
| | | |
This is a follow-up to ea70c29 to bring back the assertion error
location information provided by minitest.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 0db310586ac3e15be95d2ef27ff40cfa24c05c10.
Closes #23686.
Conflicts:
railties/test/application/test_runner_test.rb
It's possible that the `result.location` returned by minitest is outside
the test file itself. For example in the case of mocha. This resulted in
bad rerun snipptets:
```
bin/rails test app/models/deliveries/delivery.rb:103
```
Let's always use the first line of the failed test-case in our rerun
snippet. We can display the line number of the assertion error elsewhere.
|
|\ \ \
| | | |
| | | | |
mark as #:nodoc: [ci skip]
|
| | | |
| | | |
| | | | |
can’t be instantiate directly or may be no need for doc.
|
|\ \ \ \
| |/ / /
|/| | | |
remove `active_support.test_order` from environment file
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The default test order has been changed to `:random` in 5f777e4b5ee2e3e8e6fd0e2a208ec2a4d25a960d.
Therefore, it is no more need to be specified in the environment file.
|
|\ \ \ \
| |/ / /
|/| | | |
Inject Rails related configuration through Railtie
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We were explicitly referencing Rails.root in ActionCable::Server::Configuration.initialize,
thereby coupling ourselves to Rails.
Instead add `app/channels` to Rails' app paths and assign the existent files
to `channel_paths`.
Users can still append to those load paths with `<<` and `push` in `config/application.rb`.
This means we can remove the custom `Dir` lookup in `channel_paths` and the Rails
and root definitions in the tests.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
s/config\/production/config\/environments\/production/
[ci skip]
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
- Fixed related documentation and usage all around
Fixes #23561
|
|\ \ \
| | | |
| | | | |
Set database poolsize via rails_max_threads
|
| |/ / |
|