rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	Don't load app environment when editing credentials	Christos Zisopoulos	2018-12-26	1	-0/+8
\| \| \| \|	This avoids missing key exceptions caused by code that tries to read the credentials before they have been added to the encrypted file, for example when editing the credentials for a new environment.
*	Support environment specific credentials file. (#33521)	Wojciech Wnętrzak	2018-09-19	1	-5/+21
\| \| \| \| \| \|	For `production` environment look first for `config/credentials/production.yml.enc` file that can be decrypted by `ENV["RAILS_MASTER_KEY"]` or `config/credentials/production.key` master key. Edit given environment credentials file by command `rails credentials:edit --environment production`. Default behavior can be overwritten by setting `config.credentials.content_path` and `config.credentials.key_path`.
*	Recommend use of rails over bin/rails	Alberto Almagro	2018-07-06	1	-1/+1
\| \| \| \| \| \| \| \| \|	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.
*	Add an assertion that `credentials:edit` works when `RAILS_MASTER_KEY` env ↵	yuuji.yaginuma	2018-06-24	1	-1/+1
\| \| \| \|	is specified
*	Do not add master key when `RAILS_MASTER_KEY` env specified (#31922)	Yuji Yaginuma	2018-02-08	1	-0/+12
\| \| \|	Fixes #31917
*	Raise an error only when `require_master_key` is specified	yuuji.yaginuma	2017-12-18	1	-6/+20
\| \| \| \| \| \| \| \| \|	To prevent errors from being raise in environments where credentials is unnecessary. Context: https://github.com/rails/rails/issues/31283#issuecomment-348801489 Fixes #31283
*	Do not overwrite by default if credentials already exists	yuuji.yaginuma	2017-11-30	1	-0/+8
\| \| \| \|	Fixes #31286
*	Add CLI to manage encrypted files/configs.	Wojciech Wnętrzak	2017-11-15	1	-1/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	To edit/show encrypted file: ``` bin/rails encrypted:edit config/staging_tokens.yml.enc bin/rails encrypted:edit config/staging_tokens.yml.enc --key config/staging.key bin/rails encrypted:show config/staging_tokens.yml.enc ``` Also provides a backing Rails.application.encrypted API for Ruby access: ```ruby Rails.application.encrypted("config/staging_tokens.yml.enc").read Rails.application.encrypted("config/staging_tokens.yml.enc").config Rails.application.encrypted("config/staging_tokens.yml.enc", key: "config/staging.key") ```
*	Add tests for credentials command	yuuji.yaginuma	2017-09-15	1	-0/+19
\|
*	Make master key added to gitignore the same value as when creating appplication	yuuji.yaginuma	2017-09-14	1	-0/+30
	For gitignore generated by `rails new`, key with a leading slash is specified. https://github.com/rails/rails/blob/69f976b859cae7f9d050152103da018b7f5dda6d/railties/lib/rails/generators/rails/app/templates/gitignore#L11 Therefore, when executing `credentials:edit`, also need leading slack. In order to avoid such a difference, fixed to use same method for `rails new` and `credentials:edit`.