| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Stuff I see in passing while I am doing a walkthrough.
See rationale in 5b8738c.
|
|\
| |
| |
| |
| | |
y-yagi/remove_unnecessary_config_in_sprockets-rails-3
remove config that are no longer needed in sprockets-rails 3
|
| |
| |
| |
| |
| | |
`config.assets.raise_runtime_errors` and `config.assets.digest` are enabled
by default in sprockets-rails 3.
|
|/
|
|
|
| |
Defining paths relative to a file name has always hurt my soul,
with __dir__ we can restore order in the Universe.
|
|
|
|
| |
Adding period in the end.
|
| |
|
|\
| |
| | |
convert cable.coffee to cable.js
|
| |
| |
| |
| | |
In order to eliminate the dependecy of CoffeeScript.
|
|\ \
| | |
| | | |
do not set Action Cable's config when specify `--skip-action-cable` option
|
| | |
| | |
| | |
| | | |
Also remove duplicated `config.action_cable.url` config.
|
|\ \ \
| | | |
| | | | |
Delete CTRL-C message as is duplicates Puma
|
| |/ / |
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
These should allow external code to run blocks of user code to do
"work", at a similar unit size to a web request, without needing to get
intimate with ActionDipatch.
|
| | |
|
|\ \
| |/
|/|
| |
| | |
prathamesh-sonpatki/update-deprecation-message-for-app-namespace
Update deprecation message shown when tasks from rails namespace are run
|
| | |
|
|\ \
| |/
|/| |
remove rack cors initializer when updating
|
| |
| |
| |
| | |
Rack cors initializer is only necessary to API-only applications, for when the update is unnecessary.
|
|\ \
| | |
| | | |
Use app namespace for framework tasks
|
| | |
| | |
| | |
| | | |
(e.g. `rails:update` and `rails:template` tasks is renamed to `app:update` and `app:template`.)
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | | |
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
|