| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|/ / |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The `capify` command has been removed by Capistrano 3 and became to
`cap install`.
Therefore, the `capify!` method has no meaning in Capistrano 3.
I think that should deprecate.
Ref: https://github.com/capistrano/capistrano/commit/492793916acf32ffe1604daec6fd4892c8935018
|
| |
| |
| |
| | |
- [Rails <= 5.0](https://github.com/rails/rails/blob/5-0-stable/railties/lib/rails/commands/test.rb#L6) used to add the `<app_root>/test` as a string; this behaviour changed in rails 5.1, it's appending a `Pathname` object
|
| | |
|
|\ \
| | |
| | | |
Add note to Railtie docs to use unique filenames
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The fact that the names need to be globally unique was not obvious to me, so I
thought it'd be worth documenting. This not being clear was the cause of both
ctran/annotate_models#468 and instructure/outrigger#1.
[ci skip]
|
|\ \ \
| | | |
| | | | |
Drop IRB out of the web-console Gemfile comment
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We don't provide exactly the same experience as IRB does, so let's not
advertize it like that. We can say that it's an interactive console,
without further references. I have also followed byebug's comment and
changed the calling `console` part. Hopefully, this can hint that the
invocation is not view specific and you can use it like the debugger
statement.
[ci skip]
|
|\ \ \ \
| |/ / /
|/| | | |
Default Message Encryptor Cipher to AES-256-GCM From AES-256-CBC
|
| | | |
| | | |
| | | |
| | | | |
- Introduce a method to select default cipher, and maintain backward compatibility
|
| |_|/
|/| |
| | |
| | |
| | | |
Fix the mistake of not using Ruby's ENV hash from the get go and get
windows support.
|
|/ / |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
orhantoy/feature/fix-scaffold_controller-generator-usage
[ci skip] Fix `scaffold_controller` generator usage
|
| | | |
|
| | |
| | |
| | |
| | | |
We don't get any benefit from it at all.
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
greysteil/better-spacing-in-production-environment
Better spacing in environments/production.rb file
|
| | |
| | |
| | |
| | |
| | | |
Previously there were a couple of places where double-spacing or no spacing
was happening, depending on skipped options.
|
| | | |
|
| | | |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Allow a default value to be declared for class_attribute
* Convert to using class_attribute default rather than explicit setter
* Removed instance_accessor option by mistake
* False is a valid default value
* Documentation
|
| |
| |
| |
| |
| |
| | |
secrets key file that is created by rails secrets:setup"
This reverts commit 75500476eb7e953a06cc64e67ecc57b13ef8cc99.
|
|\ \
| | |
| | | |
[ci skip] Add elm option of webpack to generator description
|
| | | |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
kamipo/default_env_fall_back_to_default_env_when_rails_env_or_rack_env_is_empty_string
`DEFAULT_ENV` falls back to `default_env` when `RAILS_ENV` or `RACK_ENV` is an empty string
|
| | |
| | |
| | |
| | |
| | |
| | | |
an empty string
Follow up of #27399.
|
|\ \ \
| | | |
| | | | |
Correctly set user_supplied_options when there is no whitespace in option specification
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
specification
Current `user_supplied_options` method can not set the value correctly
if there is no space between option and value (e.g., `-p9000`).
This makes it possible to set the value correctly in the case like the above.
Fixes #29138
|
|\ \ \
| | | |
| | | | |
AEAD encrypted cookies and sessions
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit changes encrypted cookies from AES in CBC HMAC mode to
Authenticated Encryption using AES-GCM. It also provides a cookie jar
to transparently upgrade encrypted cookies to this new scheme. Some
other notable changes include:
- There is a new application configuration value:
+use_authenticated_cookie_encryption+. When enabled, AEAD encrypted
cookies will be used.
- +cookies.signed+ does not raise a +TypeError+ now if the name of an
encrypted cookie is used. Encrypted cookies using the same key as
signed cookies would be verified and serialization would then fail
due the message still be encrypted.
|
| | |
| | |
| | |
| | | |
Fixes #29247
|
| | | |
|
|\ \ \
| | | |
| | | | |
Define path with __dir__
|
| |/ /
| | |
| | |
| | |
| | |
| | | |
".. with __dir__ we can restore order in the Universe." - by @fxn
Related to 5b8738c2df003a96f0e490c43559747618d10f5f
|
|\ \ \
| | | |
| | | | |
Make `secrets:edit` run `secrets:setup` if it hasn't already.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Setup config/secrets.yml.enc with template contents for people to edit.
Then generate encryption key and encrypt the initial secrets.
|
| |/ /
| | |
| | |
| | |
| | | |
Needed back when we attempted to wait for editors, but now we expect
users to pass a -w flag to their $EDITOR.
|
| | |
| | |
| | |
| | | |
with it
|
|/ / |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
| |
It wasn't clear that system tests don't run with the rest of the test
suite and are part of a separate command.
This documents the `test:system` command as well as update the Rails
runner help documentation to make it clearer that system tests are run
via their own command by default.
|
|\
| |
| | |
Allow irb options to be passed from `rails console` command
|
| |
| |
| |
| | |
Fixes #28988
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
y-yagi/allow_to_receive_arbitrary_arguments_in_aggregated_results
Allow to receive arbitrary arguments in `aggregated_results`
|
| |/
| |
| |
| |
| | |
Argument was added to `aggregated_results` in minitest 5.10.2.
Ref: https://github.com/seattlerb/minitest/commit/c6ba2afd90473b76d289562edd24f7d7ca8484f9
|
|/
|
|
|
|
| |
Capybara 2.14.0 was released. Loosen the tight constraint in the
generated Gemfile, so that Rails applications can take advantage of the
new version
|