The couple projects that I've seen do this put a standard database.yml at database.yml.example (or similar) and keep their custom version elsewhere. You could .gitignore it and then symlink it in with Capistrano post-deploy, for instance.
--Matt Jones On Aug 22, 10:33 pm, davetron5000 <[email protected]> wrote: > I have a Rails app that I'm sharing via GitHub, but that I'm also > using on my website. It has some configuration options that I don't > wish to share, but that I'd like version controlled. I'd also like to > make it difficult or impossible for me to accidentally push these > config changes up to GitHub. > > What is the best practice or convention here? > > The only option I could come up with (other than just not versioning > these files), is to keep them on a private branch that I never push to > GitHub. > > Any other good ways to go about this? > > Dave --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
