| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The default is that's false, caching even if you do not specify the caching option is determined not to use,
and `tmp/caching-dev.txt` will be deleted.
If it is this, regardless of whether or not there is `tmp/caching-dev.txt`, be sure to order would be necessary to specify the caching option,
I think that in than good to so as not to do anything by default.
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | | |
The logger interface to get all Rails features is not obvious. This change adds documentation on how to assign a logger that will use all Rails features.
We are also matching the stdout logging interface to the default logger in bootstrap https://github.com/rails/rails/blob/f5a5988352b165143f0f9d622707c351c1470882/railties/lib/rails/application/bootstrap.rb#L42-L45.
|
| |/
|/|
| |
| |
| | |
Lets have the server and the Rake task go through the same ropes, so we can
share all the file lookup, adding, and deleting code.
|
| |
| |
| |
| |
| |
| |
| | |
If we're gonna do this right, it will look mighty different from this anyway.
(Looking at you, Rails 5.1).
It isn't being used in any code as of now, so yanking is the best option.
|
| | |
|
|\ \
| | |
| | | |
Remove passing `with_dispatchers` to AppGenerator
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- While working on https://github.com/rails/rails/pull/22790 I found out
that we pass `with_dispatchers: true` but it's not used at all by Rails.
- We were passing `with_dispatchers: true` in few tests too but again
it's not used by Rails.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit comes from the comments made by @matthewd at https://github.com/rails/rails/pull/23795/files#r54469637
and by @rafaelfranca at https://github.com/rails/rails/pull/23795/files#r54609364
The idea is that if you type (for example) "rake db:migrate" in an AppGenerator,
then this should actually invoke `rake db:migrate` on the command line, whereas
if you type "rails_command db:migrate", this should invoke `rails db:migrate`.
|
|\ \ \
| | | |
| | | | |
Remove redundant regexp escapes in generators
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
In the latest version of Web Console, you can call `console` anywhere in
your application and get a console with that binding in it. I think this
is worth advertising, as it may be useful to do outside of controllers
and views.
[ci skip]
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Between major versions 2 and 3, we hit a bug. It's fixed in version 3,
however, the explicit 2.x requirement of `~> '2.0'` will prevent people
from getting the fix with `bundle update` and they would have to
explicitly set the constraint to `~> '3.0'`.
For more information see: rails/web-console#178.
I propose we drop the explicit version constraints in the Gemfile. Web
Console has been relatively stable for the past couple of years, and I
don't anticipate any major alterations, like we saw between major
versions 1 and 2.
|
| | |
| | |
| | |
| | | |
Reads much better doesn't it.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Stuff I see in passing while I am doing a walkthrough.
See rationale in 5b8738c.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Stuff I see in passing while I am doing a walkthrough.
See rationale in 5b8738c.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Stuff I see in passing while I am doing a walkthrough.
See rationale in 5b8738c.
|
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|