Don't push any of it to Heroku. Storing SSL keys or other credentials in a repo is really bad practice. If you ever want to let a contractor or third party edit your sources, you're basically handing him keys to the kingdom, not to mention, it's costly and hassle-prone if you ever have to rotate your keys.
Instead, upload them as specified in the document you reference -- note that this doesn't involve putting them in your repo -- and store them somewhere safe, like a hard disk with a decent backup service. To the best of my knowledge, Heroku's SSL config can't read keys out of a repo anyway, so why put them there in the first place? On Tue, Jan 24, 2012 at 1:46 PM, fearless_fool <[email protected]> wrote: > I've just followed the directions for setting up SSL on Heroku (c.f. > http://devcenter.heroku.com/articles/ssl), during which the following > files were created: > > # final.crt > # gd_bundle.crt > # secure.mysite.com.crt > # site.csr > # site.key > # site.orig.key > > It's evident that final.crt will be installed on Heroku. > > It would be convenient for me to add these files to my git branch and > push them to Heroku, but is that prudent? Specifically, is there any > sensitive info in any of these files that should NOT be pushed? > > - ff > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
