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
Based on a discussion in the Ruby North east channel which originated from rails thread rails/rails#25095,
It seems encrypted variables could be a very useful feature for larger teams who don't want to cycle variables, but a more transparent approach than ejson would be preferred. This would also add security to production deployments where the configuration is shared.
Tying this into the global rails config/secrets.yml would simplify integration and share the same security as encrypted cookies.
Based on a discussion in the Ruby North east channel which originated from rails thread rails/rails#25095,
It seems encrypted variables could be a very useful feature for larger teams who don't want to cycle variables, but a more transparent approach than ejson would be preferred. This would also add security to production deployments where the configuration is shared.
Tying this into the global rails
config/secrets.yml
would simplify integration and share the same security as encrypted cookies.Inspirations:
The text was updated successfully, but these errors were encountered: