Rails core - Sep 2005 - New stuff discussed

Hey guys great job on the new environment.rb dsl and rakefile.
I switched shopify over to the new layout and here are some thoughts:

  * The environment.rb doesn''t set the RAILS_ENV anymore. In the typo  
world the most common way to set typo to production mode is to change  
the default to production in the environment.rb. Most of the time  
people install on shared host and can''t influence the ENV vars the  
server passes to the apps.

  * The new environment.rb should have more inline documentation.  
Routes.rb did a good job by being mostly self documenting, how about  
figuring out the most common modifications to the standard config and  
leaving them as comments in the file?

  * The rake file looks in config/tasks. I don''t think that rake  
tasks really have anything to do with the config. I think there is  
some value in keeping this directory as lean as possible because this  
is what end users of rails apps have to work with who are not  
necessarily familar with rails itself. We ship with a lib folder by  
default so what about lib/tasks? Fits better in my book because you  
will most likely bring your favorite rake tasks from project to  
project which makes them great fits for the lib directory.

  * boot.rb is a good file but doesn''t really have anything to do  
with config/ maybe move it to config/environment/ ?

  * The project local generators path was broken until recently so if  
we will introduce a lib/tasks folder this would be a good opportunity  
to move the generators to lib/generators as well. This way you don''t  
mess up tab compleation for ./script/g<tab>


--
http://www.snowdevil.ca      - Snowboards that don''t suck
http://typo.leetsoft.com        - Open source blog software
http://blog.leetsoft.com     - Technical weblog

>   * The environment.rb doesn''t set the RAILS_ENV anymore. In the
typo
> world the most common way to set typo to production mode is to change
> the default to production in the environment.rb. Most of the time
> people install on shared host and can''t influence the ENV vars the
> server passes to the apps.
You can still set it by using ENV[''RAILS_ENV''], I''ll
add that as a comment.
 
>   * The new environment.rb should have more inline documentation.
> Routes.rb did a good job by being mostly self documenting, how about
> figuring out the most common modifications to the standard config and
> leaving them as comments in the file?
I agree.
>   * The rake file looks in config/tasks. I don''t think that rake
> tasks really have anything to do with the config. I think there is
> some value in keeping this directory as lean as possible because this
> is what end users of rails apps have to work with who are not
> necessarily familar with rails itself. We ship with a lib folder by
> default so what about lib/tasks? Fits better in my book because you
> will most likely bring your favorite rake tasks from project to
> project which makes them great fits for the lib directory.
I agree, again ;)
>   * boot.rb is a good file but doesn''t really have anything to do
> with config/ maybe move it to config/environment/ ?
I don''t think book is a better fit in environment. I think that dir
deserves more to be kept clear of everything but the three environment
files. I do think that boot.rb semantically fit the role of
configuration, but it wouldn''t be there unless it had to (since the
user should very rarely if ever have to edit it).
>   * The project local generators path was broken until recently so if
> we will introduce a lib/tasks folder this would be a good opportunity
> to move the generators to lib/generators as well. This way you
don''t
> mess up tab compleation for ./script/g<tab>
Sounds like a good idea too.
-- 
David Heinemeier Hansson
http://www.loudthinking.com -- Broadcasting Brain
http://www.basecamphq.com   -- Online project management
http://www.backpackit.com   -- Personal information manager
http://www.rubyonrails.com  -- Web-application framework