skeleton and configs

[Chris Farmiloe]

Hi people, just thought I'd mumble out my thoughts on merb's apps  
directory structure and config concepts and see what other people are  
feeling...


the app dir:
	mvc/application is layed out as expected....maybe
	without the mailer by default (another discussion)

the config dir:
	I really think that it's confusing to have such a
	mixture of ways to configure some of the settings
	merb.yml, 3xenvironment .rb files, a dependancies.rb
	an init file and potenially an upload.conf.
	
	wouldn't it be nicer to just have a very well commented
	init.rb to contain ALL the app setup and options?
	the well commented options in merb.yml works well as
	a quick stop for what can be tweaked, but that same
	concept would work equally well in an .rb file and make
	merb's startup sequence obvious and clear without any
	special knowledge.

the deps & lib dirs:
	Almost every ruby library, gem, or application has a lib
	dir to contain the required files. This is a kind of standard
	by consistantcy. Why does the "deps" dir exist?. A /plugins
	dir would feel equally at home in lib/plugins and it would
	solve the minor dilemor of "does my little extension count
	as a "dependancy" or as a "lib"

the log dir:
	can't argue there.

the public dir:
	that's a given.

the schema dir:
	I think this should be created by whichever ORM plugin/lib
	you have chosen to use. Not all merb apps will even need
	a database.

the spec dir:
	perfect, one single obvious place to get your mocks/specs
	in order

the scripts dir:
	this should be removed. Raketasks are to "scripts" as merb
	is to actionpack ;)  ....and "rake -T" is your friend.





Regards

chrisfarms.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/merb-devel/attachments/20070922/fe58afde/attachment-0001.html