On 6/15/07, Michael Koziarski <[EMAIL PROTECTED]> wrote:
> > # config/environments/live.rb
> > acts_like :development
> Can't you just require common pieces of code from each of the
> environments? If not, perhaps we should make that simpler to do.
In the case of two environments that share common pieces of code,
absolutely. Where I've found this most useful, though, is in a case
where an environment is either *precisely* the same as another (except
for the database, e.g., running with a copy of live data on your local
dev machine), or differs in the most minor of ways.
This is really just a bit of sugar, of course. It's the equivalent of:
# in config/environments/live.rb
# live should act exactly like development, except for the database
eval(IO.read("#{RAILS_ROOT}/config/environments/development.rb"))
As sugar, it may not be a good addition. I sure think "acts_like
:development" is nice, though.
> The initializers feature also takes care of a lot of the duplication I
> used to have between 'production' and 'staging' at present, what
> stuff are you left with in both files?
Love the initializers. Leftover differences between, say, production
and staging are mostly totally reasonable stuff, like email addresses
or server names/IP's.
~ j.
--~--~---------~--~----~------------~-------~--~----~
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 [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-core?hl=en
-~----------~----~----~----~------~----~------~--~---
