Re: [Rails] Re: Rails 5.2 Custom Credentials — generally accepted way to segregate environments?

In the mean time you can add a rake task to the lib folder to rename credentials, or a bash/Ruby script to the bin folder: Given: development.yml.enc, test.yml.enc, production.yml.enc lib/tasks/credentials.rake namespace : credentials do namespace :set_env do task production: :

Re: [Rails] Re: Rails 5.2 Custom Credentials — generally accepted way to segregate environments?

I think this solution seems the most Rails 5.2 friendly, but ideally isn't the perfect solution as ideally you could in fact (one day, in Rails 6, say), separate the 3 files themselves, so you could, say, give junior developers access to only development+staging credentials by giving the only

[Rails] Re: Rails 5.2 Custom Credentials — generally accepted way to segregate environments?

for rails 5, just nest environment specific credentials under a key for said environment then all you have to do when accessing said config is add the environment to the party that pulls in config, e.g.: credentials.yml.enc: main_key: development: sub_key: value_key: 'development'

[Rails] Re: Rails 5.2 Custom Credentials — generally accepted way to segregate environments?

I've found the rails-env-credentials gem useful for this. Not sure how compatible it will be with the upcoming Rails 6 support but its been working great for my app. Eric On Sunday, June 9, 2019 at 9:40:05 PM UTC-4, Jason Fleetwood-Boldt