diff options
| author | Alberto Almagro <albertoalmagro@gmail.com> | 2018-06-26 22:02:51 +0200 |
|---|---|---|
| committer | Alberto Almagro <albertoalmagro@gmail.com> | 2018-07-06 22:46:35 +0200 |
| commit | 40b209db53796ae515387d0fee2a525872eb2ae4 (patch) | |
| tree | 604a386af44a319c9cb136b9e1e260e7c59a4d7c /railties/lib/rails/commands/secrets/USAGE | |
| parent | a0061d2389a178b093f0d3f64f58236ffbe088e0 (diff) | |
| download | rails-40b209db53796ae515387d0fee2a525872eb2ae4.tar.gz rails-40b209db53796ae515387d0fee2a525872eb2ae4.tar.bz2 rails-40b209db53796ae515387d0fee2a525872eb2ae4.zip | |
Recommend use of rails over bin/rails
As discussed in #33203 rails command already looks for, and runs,
bin/rails if it is present.
We were mixing recommendations within guides and USAGE guidelines,
in some files we recommended using rails, in others bin/rails and
in some cases we even had both options mixed together.
Diffstat (limited to 'railties/lib/rails/commands/secrets/USAGE')
| -rw-r--r-- | railties/lib/rails/commands/secrets/USAGE | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/railties/lib/rails/commands/secrets/USAGE b/railties/lib/rails/commands/secrets/USAGE index 96e322fe91..e205cdc001 100644 --- a/railties/lib/rails/commands/secrets/USAGE +++ b/railties/lib/rails/commands/secrets/USAGE @@ -7,7 +7,7 @@ with the code. === Setup -Run `bin/rails secrets:setup` to opt in and generate the `config/secrets.yml.key` +Run `rails secrets:setup` to opt in and generate the `config/secrets.yml.key` and `config/secrets.yml.enc` files. The latter contains all the keys to be encrypted while the former holds the @@ -45,12 +45,12 @@ the key. Add this: config.read_encrypted_secrets = true -to the environment you'd like to read encrypted secrets. `bin/rails secrets:setup` +to the environment you'd like to read encrypted secrets. `rails secrets:setup` inserts this into the production environment by default. === Editing Secrets -After `bin/rails secrets:setup`, run `bin/rails secrets:edit`. +After `rails secrets:setup`, run `rails secrets:edit`. That command opens a temporary file in `$EDITOR` with the decrypted contents of `config/secrets.yml.enc` to edit the encrypted secrets. |