[Nitro] Nitro dir structure

[Jonathan Buch]

Hi,

> so perhaps this pattern would work for nitro too? but in nitro's case
> the distribution (and versioning) actually includes this website
> container as the starter app? in other words maybe the proto app should
> exist over the nitro system rather than under or parallel to it. just a
> thought.

This layout would imply that the whole tree (app source) would be
accessable from the outside (browser) if you don't deny access to that
folder by using an Apache .htaccess file or other configuration options
provided by the webserver.

> (hmm... i see maybe some other advantages too... the repo dir (or
> whatever you want to call it) could be soft linked to a shared location
> and the proto app could be a "reconfigurable" app, ie. a gen-based web
> app. yes, i'm a dreamer ;-)

Well, as Nitro (meaning the nitro app) is practically your server (even if
cgi based), the application can reside anywhere.  The only thing the
webserver (any proxy, mongrel, fcgi client, etc) has to know (besides the
nitro app server) is the path to the public files.  So the public/ folder
is completely decoupled from the nitro app.

Your proposed folder layout is doable, but it's 'upside down' IMO.

Jo

-- 
Feel the love
http://pinkjuice.com/pics/ruby.png