-
Notifications
You must be signed in to change notification settings - Fork 240
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
config/secrets.json unable to be included for Heroku deployment #309
Comments
I'd also like to mention.. running: |
Alright so here's what i've discovered thus far and this will require some code edits of some sort im sure. If you create a
you commit, and push it to heroku you will have a starter template secrets.json file.. You can then run a bash prompt on heroku... I could tell this by running This is probably because when you start the app im guessing it writes into memory the secret: hash.. One step closer, as you can actually get heroku to create the secrets.json hash string just can't get geddy to recognize it. |
Ruby on Rails allows developers to use ERB syntax within config yaml files. IMHO maybe Geddy can provide something similar to Ruby on Rails? |
This is actually not a bad idea. You could easily include environment On Sun, Jun 23, 2013 at 9:48 AM, MrOrz notifications@github.com wrote:
|
NM, implemented in bfa7650, pushed to master. Just commit your secrets.json file to Git (i.e., remove from the .gitignore), and use EJS with environment variables so your secrets don't end up in revision control. |
Wow that was fast! :D |
Sweet! I've been looking forward to this too. +1 |
Since Heroku is deployed via Git, and config/secrets.json is in .gitignore it's impossible to deploy if you need it.
The text was updated successfully, but these errors were encountered: