| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / |
|
| | |
|
|\ \
| | |
| | | |
Use web_console 2.0 for 4.2.0.rc1 release
|
| | |
| | |
| | |
| | |
| | | |
This one replaces the notable web-console mentions in guide and the
default Gemfile.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If you run a generator such as:
```
rails generate model accounts supplier:references
```
The resulting migration will now add the corresponding foreign key
constraint unless the reference was specified to be polymorphic.
|
|/ / |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts deprecations added in #13528.
The task is brought back for two reasons:
1. Give plugins a way to hook into the test database initialization process
2. Give the user a way to force a test database synchronization
While `test:prepare` is still a dependency of every test task, `db:test:prepare`
no longer hooks into it. This means that `test:prepare` runs before the schema
is synchronized. Plugins, which insert data can now hook into `db:test:prepare`.
The automatic schema maintenance can't detect when a migration is rolled-back,
modified and reapplied. In this case the user has to fall back to `db:test:prepare`
to force the synchronization to happen.
|
| |
| |
| |
| |
| |
| | |
The tests to verify our testing setup used `RAILS_ENV=development`
to execute the tests. Let's keep it as close to a real-world setup
as possible.
|
| |
| |
| |
| |
| |
| | |
Closes #17756
[Godfrey Chan, Zachary Scott]
|
| |
| |
| |
| | |
This removes the unwanted deprecation warnings in the tests
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a follow-up to 116de07. That change was for two reasons: 1) speed up the
tests by reducing the amount of log lines 2) avoid a deprecation warning from
a6de6f5.
This setting need to be on the basic app too, otherwise the deprecation warning
will show up on other unrelated test cases.
|
|\ \
| | |
| | | |
Always default the log_level to :info for Railties
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Add a CHANGELOG entry for #16622 and a6de6f5 [ci skip]
|
| |/ |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Creating mailer layouts by default, including html and body tags
|
| | | |
|
| | |
| | |
| | |
| | | |
tags to reduce spam score
|
| |/
|/|
| |
| |
| |
| | |
- Remove sprockets-rails from generated Gemfile as rails has a hard-dependency on it
- Also allow sprockets-rails >= 2.0.0
|
|\ \
| | |
| | | |
Replace ActionDispatch::Head with Rack::Head.
|
| | | |
|
| | |
| | |
| | |
| | | |
I put the wrong path in my last PR by accident. Fixed here. Related to #17742
|
|/ /
| |
| |
| |
| |
| | |
Currently, the docs uses a syntax that is unclear and not general
American English. I've switched it to be clearer wording. Not a big
fix, but may be helpful.
|
| |
| |
| |
| |
| |
| |
| |
| | |
We generate a `.keep` file inside the log directory to make
sure the directory itself is under version control. let's keep
it that way.
/cc @matthewd
|
|\ \
| | |
| | |
| | |
| | |
| | | |
why not gitignore /log as a whole?
[ci skip]
|
|/ / |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Skip spring install in Cygwin due to fork() bad support.
|
| |/
| |
| |
| | |
See also: https://www.cygwin.com/faq.html#faq.using.fixing-fork-failures
|
|\ \
| | |
| | | |
Minor English fixes in docs [ci skip]
|
| |/ |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This is a more conservative approach to 2602a49. Also changed the comment to be
more inline with everything else in the file (describing what the config value
is doing and why). People should just read the docs for alternatives.
|
|/
|
|
|
|
|
|
|
| |
This reverts commit 2602a49a8600ab52f807599bbd5b1f9c0be4214f, reversing
changes made to 5d7c1057684c377bc2801c8851e99ff11ab23530.
The explicit default was introduced in 21f6d72, so apps created with Rails < 4
have the commented out version, which means that this change would break those
apps.
|
| |
|
|\
| |
| | |
Fix Rails::Paths::Path.unshift interface
|
| | |
|
|\ \
| |/
|/| |
simplify rake test vs rake test:all
|
| |
| |
| |
| | |
Renames `rake test:all` to `rake test` by changing old `rake test:run` to previous version of `rake test:all`. Removes old definition of `rake test`. Also renames `rake test:all:db` to `rake test:db` and deprecates `rake test:all` & `rake test:all:db`
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Replaces the following in two places:
```diff
-require ::File.expand_path('../config/environment', __FILE__)
+require ::File.expand_path('../config/environment', __FILE__)
```
|
| | |
|
| |
| |
| |
| | |
Just prefer secrets over config
|
|\ \
| | |
| | |
| | | |
Allow fallback to LegacyKeyGenerator when secret_key_base is not set but secrets.secret_token is
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- `secrets.secret_token` is now used in all places `config.secret_token` was
- `secrets.secret_token`, when not present in `config/secrets.yml`,
now falls back to the value of `config.secret_token`
- when `secrets.secret_token` is set, it over-writes
`config.secret_token` so they are the same (for backwards-compatibility)
- Update docs to reference app.secrets in all places
- Remove references to `config.secret_token`, `config.secret_key_base`
- Warn that missing secret_key_base is deprecated
- Add tests for secret_token, key_generator, and message_verifier
- the legacy key generator is used with the message verifier when
secrets.secret_key_base is blank and secret_token is set
- app.key_generator raises when neither secrets.secret_key_base nor
secret_token are set
- app.env_config raises when neither secrets.secret_key_base nor
secret_token are set
- Add changelog
Run focused tests via
ruby -w -Itest test/application/configuration_test.rb -n '/secret_|key_/'
|
| | |
| | |
| | |
| | | |
active_support/notifications [ci skip]
|