On Jun 12, 2008, at 3:13 PM, Ezra Zygmuntowicz wrote:
> I have to chime in here and plead for you to leave the database.yml
> alone. Or if you must use ruby config, please leave the db.yml
> working. If the credentials/config is only in ruby and in the local
> variable format you showed earl
On Jun 12, 2008, at 11:40 AM, James Adam wrote:
>
> I guess this boils down to - why generate the Hash, when just writing
> the Hash is pretty much equally readable? Do we get some benefit using
> the block/DSL-style syntax? If not, the implementation could perhaps
> be simpler.
>
Running it thro
On Jun 12, 2008, at 9:28 AM, Chad Woolley wrote:
>
> So, I hope Rails still natively supports the old YAML format after
> this patch, to support old tutorials, and to provide a standardized
> option when it is needed, such as Rails parsing geminstaller.yml if it
> exists, or a hosting company pars
On Jun 12, 2008, at 5:47 AM, Rick Olson wrote:
>> That's also a lot harder to read and write, especially for
>> newbies. I
> definitely support an all-ruby approach. Supporting some generic hash
> merging, as Scott suggested, might not be a bad idea though.
>
Something like this is ugly, but
On Jun 11, 2008, at 11:55 AM, Ben Munat wrote:
>
> 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
On Jun 11, 2008, at 11:41 AM, Mislav Marohnić wrote:
> 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 think
On Jun 11, 2008, at 9:12 AM, Mislav Marohnić wrote:
> What I like with database.yml is that I don't version it and
> therefore I don't keep production passwords in version control. Also
> I can have one database in production locally and another on the
> remote machine.
>
I've done that t
In short: With the help of the friendly folks in #rails-contrib, I've
been working on a patch that provides Ruby configuration of your
database connections. I'm looking for people to test the patch and
post +1s if it works for them. You can find the patch in Lighthouse:
http://rails.lightho
