sounds fine to me.
I have a separate issue with having a static single-environment
configuration like this because it's the root cause of some other problems
I've had with database configuration, but describing that would just
confuse this issue and can wait til another day.
thanks for your respo
Brian, I see your point.
I actually think that this project will actually benefit you. My goal is to
standardize the api in which ActiveRecord and ActionMailer are configured.
I don't think I can decide to make this public, but I think that with the
standardization will also come API stability.
A
if anything, I'd rather see database.yml go away and have AR configured
through the application config api instead. the current state of affairs
makes it more difficult to e.g. use an external configuration repository
like ZooKeeper. that will continue to be true as long as AR has no
documented pub
Richard,
I agree that storing configuration in git is not ideal.
My hope is that:
1. moving mail configuration to mail.yml will encourage mail configuration
to be treated more like database configuration is now (by default,
database.yml is not included in git; and a database.yml.example is
provi
Storing configuration in your git repository is not the greatest thing on
earth: http://www.12factor.net/config
At least by pulling it from code it becomes very easy to assign to ENV
Variables.
--
Richard Schneeman
http://heroku.com
@schneems (http://twitter.com/schneems)
On Sunday, Ma
Hello,
TL;DR: I'd like to move ActionMailer configuration to confg/mail.yml (just
like config/database.yml). In order to make that possible (in a sane way),
I would like to standardize the way ActiveRecord and ActionMailer are
configured.
As I was poking around to see how I would implement confi
