On Sep 22, 2007, at 9:27 AM, Chris Farmiloe wrote:
On 22 Sep 2007, at 14:45, Wayne E. Seguin wrote:
>> config/environments/{production,staging,testing,development,...}.rb
Reading over my post it did seem I implied that I wanted to scrap
the environments.
Sorry, that's not what I meant ... the environment structure is
very useful.
I was more talking about combining all the others.
basically leaving us with.
router.rb
init.rb
environments/development.rb
environments/production.rb
environments/stage.rb
environments/test.rb
if some options [ala Merb.add_mime_type] are to be set via ruby
code, then lets set them ALL via ruby code and make init a nice
linear file that is clearly the app's boot script.
I thought it very odd to follow the execution path around these
files (especially when a line in merb.yml specifies the location of
another yaml file for the upload.conf!)
I agree about the difficulty of following the execution path--
ideally, we should make this as straight-forward as possible by
defaulting to a single init.rb or merb_init.rb file. For example,
why not use a case/when statement instead of the environments/*.rb
situation? Just a thought.
The only exception I can think of is keeping the dependencies.rb file
around--as has been discussed before, we need some way to keep this
separate so that "rake" has a way of knowing what to load (without
loading the whole application) and can thus add all rake tasks from
the dependencies.
Duane Johnson
(canadaduane)
_______________________________________________
Merb-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/merb-devel
