In the 5.1 version, encrypted secrets were introduced, and were handled by the file along with the encryption key control. The alternate method saved secrets in the secrets.yml file and avoided committing it to the repository. This had many safety constraints in place. The first method stored secrets in the environment variable (secret_key_base) and committed the secrets.yml file to the repository.

Initially, there were two methods to handle secrets. Post version updates, handling secrets has become easier. RAILS_MASTER_KEY='your_master-key_content'Īny rails program would have secrets to be stored, for at least the secret key base with tokens for third-party APIs. The former option is preferred, but as you haveįile under app's root and put there a line Should be augmented with this key some way. After the deployment, which usually involves Git repository, generated by default Rails application setup, includes These credentials are encrypted with the key stored inįile. Rails 5.2 and later uses encrypted credentials for storing sensitive app's information, which includesīy default. , and I have the good key displayed (GENERATED_KEY_1)Īnd added Dotenv to my Gemfile, required it in application.rb On my console, server-side, as deploy user.

Here is the thing, I'm not sure if the followings steps are the goods one. On his console app-side, he add a file /my_website/.rbenv-vars with a SECRET_KEY_BASE line, filled with the generated secret key), I decided to follow the multiples topics answering to this question. For ' production' environment, set this string withĪs the method of Gorails didn't seems to work (after a

Generate rails master key