farcry deployment directory structures

Folks,

Am having a play with the notion of a cloud based platform option for 
FarCry 7 installations.  Initially this is something I want to run for some 
of our smaller clients who currently fall into the "Premium Shared Hosting" 
bucket.  However, there's no reason this couldn't be expanded to anyone 
interested in running a full blown farcry installation in a no hassle cloud 
platform.

Something that I need to get a handle on is how people commonly deploy 
FarCry for their own installations. FarCry is very flexible (perhaps too 
flexible) in the way it lets you deploy your application.  Despite this 
flexibility I wonder if there aren't just a few common approaches used by 
everyone.

Daemon frequently deploys apps as follows:

d:/webapps <- some server location
d:/webapps/mywebapp <- [approot] of an entire app install

[approot]/core <- location for core framework
[approot]/plugins <- all plugins go here
[approot]/projects/mywebapp <-project files

[approot] == /farcry mapping (typically Apache Alias)
[approot]/projects/mywebapp/www <- doc home for website

How do you deploy FarCry?

-- geoff
http://www.daemon.com.au/
twitter. @modius

-- 
You received this message cos you are subscribed to "farcry-dev" Google group.
To post, email: farcry-dev-/[email protected]
To unsubscribe, email: farcry-dev+unsubscribe-/[email protected]
For more options: http://groups.google.com/group/farcry-dev
--------------------------------
Follow us on Twitter: http://twitter.com/farcry
--- 
You received this message because you are subscribed to the Google Groups "farcry-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to farcry-dev+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/[email protected]
For more options, visit https://groups.google.com/groups/opt_out.