You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's create a development.key, test.key, run the rails commands to set up each of their credential files. All those can be committed to the repo.
Remove the secrets file. Update the .gitignore.
Either @colinxfleming or @lomky will handle generating the production.key and its corresponding credential file before merging, updating the production env var, & releasing it!
Anything else?
S/o to the work done in #3128 & #3220 for kicking this off!
The text was updated successfully, but these errors were encountered:
Thanks for creating an issue! Please fill out this form so we can be sure to have all the information we need, and to minimize back and forth.
Right now we use the (quite old) style secrets file. Let's move over to using the new-style
configs/credentials/
filesKeeping up with Rails Norms
After a bit of research, let's follow the per-env key migration route. That best matches our current setup.
This article has a good step by step.
Let's create a
development.key
,test.key
, run the rails commands to set up each of their credential files. All those can be committed to the repo.Remove the secrets file. Update the .gitignore.
Either @colinxfleming or @lomky will handle generating the
production.key
and its corresponding credential file before merging, updating the production env var, & releasing it!S/o to the work done in #3128 & #3220 for kicking this off!
The text was updated successfully, but these errors were encountered: