I do this with a production.rb.tmpl template file with everything ready to go except for the things which can't go into the repo, like passwords. Upon deploy I use this to construct the actual production.rb file.
Another option is to put the password into an environment variable on the production box, and use that (ENV["smtppass"] or something) in the config file. Or -- which I would do if it was only about smtp -- set up sendmail/postfix on the production box to use an SMTP smarthost. That way, you can let Rails use sendmail, and sendmail will forward it to another smtp server of your choice (with the possibility of authentication). - Marten On Mon, 18 Jan 2010 23:11:07 -0800 (PST), Mario <mflor...@gmail.com> wrote: > Hi, > > I'm working on a RoR website for an non-profit and we want to put the > code up on github as a public repo (my first public repo). The only > issue I'm having is that we use an SMTP connection to send email and > are storing the password in our environments/production.rb file. Are > there any best practices I should adhere to? Or does anyone have any > suggestions on how they've handled this issue? > > Thanks for the help! > > -Mario > -- > You received this message because you are subscribed to the Google Groups > "GitHub" group. > To post to this group, send email to git...@googlegroups.com. > To unsubscribe from this group, send email to > github+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/github?hl=en. > > -- - Marten -- You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to git...@googlegroups.com. To unsubscribe from this group, send email to github+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/github?hl=en.
