I think your intuition about database.yml is right on. Following that example, you could make, say, a passwords.yml file, and be careful not to include it in the source repository. For a bit more security, you could use a symlink to a file somewhere outside of your project directory.
Michael On Wed, Jun 25, 2008 at 3:45 AM, Antony Evans <[EMAIL PROTECTED]> wrote: > > Hiya, > > I'm building an app on top of the insoshi engine. It needs to > interface with a third party application via http protocols (I'm using > Rest_client as a wrapper). This application requires a password, > which obviously I don't want to put out on the web for the whole world > to see. What best practice for managing this password issue and still > make my code open source? Presume to use something along the lines of > the database.yml file which isn't included within the git. > > Thanks, > Antony > > > -- Michael Hartl Insoshi social software http://insoshi.com/ --~--~---------~--~----~------------~-------~--~----~ Insoshi developer site: http://dogfood.insoshi.com/ Insoshi documentation: http://docs.insoshi.com/ You received this message because you are subscribed to the Google Groups "Insoshi" 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/insoshi?hl=en -~----------~----~----~----~------~----~------~--~---
