Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make a lesson on secrets #8

Open
jrhorn424 opened this issue Feb 23, 2016 · 4 comments
Open

Make a lesson on secrets #8

jrhorn424 opened this issue Feb 23, 2016 · 4 comments
Labels

Comments

@jrhorn424
Copy link

Currently best practices are scattered among a few repos. A single repo would probably be a valuable reference for developers in the future.

Original: ga-wdi-boston/rails-heroku-setup-guide#6

@gaand
Copy link

gaand commented Feb 24, 2016

@jrhorn424 Should this be a study?

@jrhorn424
Copy link
Author

Perhaps. There's an iceboxed repo here: https://github.com/ga-wdi-boston/secrets

@jrhorn424
Copy link
Author

Should this become a priority for 014? If so, I'd expand the scope to include a discussion of environment variables in general. Lots of confusion around environment variable naming with express deployment in 012. @ga-wdi-boston/core

@gaand
Copy link

gaand commented Aug 28, 2016

If you think you have the cycles. Connecting the environment with [rails]-dotenv and heroku config would be a good thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants