Mislav Marohnić wrote: > On Wed, Jun 11, 2008 at 17:04, Adam Keys <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > > Or you can stick with database.yml :) > > > I will stick with yml for sure and I guess most of experienced devs will > also keep their copies because, now that we have deployment set up, > there is no compelling reason for us to switch. > > But I'm worried what about new users? This pratice encourages them to > version their passwords. Rails is opinionated and we have to choose > which practice we will encourage. Will it be database info in ruby or YAML?
I don't understand how a Ruby config encourages versioning passwords more than using the yaml file. Either way you can svn/git ignore the file with the passwords. However, the main benefit of switching to a Ruby config file seems to be "because database.yml was the only yaml config file", which doesn't seem like a particularly great reason. On the other hand, I like this just because I find the Ruby syntax more clearly indicates what you are doing, whereas the yaml is pure data that is sucked up into some mysterious place inside Rails. So I guess that's more than a "just because it's not yaml" reason. Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
