> Also, I appreciate your efforts to contribute to the thread, and the fact
that you have to maintain your propriety. However, Daemon has a vested interest in creating a definitive tutorial (prob. better than "faq" or "whitepaper") that spells out step-by-step best practices for shared hosting environments. It sounds as if your setup is manual which is likely the only way this is possible at the moment, but I would love to see Daemon include in a tutorial on procedures for self-configuration (if possible) on a shared host, with risk-reduction tips for the hosts themselves. Obviously, better yet, would be a more feature-rich install program that would allow automated configuration.
Hopefully a representative from Daemon will comment on this request.
I don't think setting up FarCry is the concern here, I think it's more to do with the monitoring of bandwidth for each site and other administration concerns for the host (as Guennadi has mentioned).
Setting up FarCry is very simple. The host is required to have one directory for all FarCry applications, let's call it www for example. To begin with the directory will contain the following:
www/farcry_core www/fourq
A coldfusion mapping called "/farcry" needs to point to this www directory (as is the case in all farcry setups).
For each new site that needs to be added to the server a datasource, database and farcry project directory need to be added. No installs should ever been done on a production server. The site should be installed, developed and tested in a staged environment and the go-live process should simply be an ftp of the code base and a database migration.
So after a few farcry sites have been put on the server the www directory may look like this:
www/farcry_core www/fourq www/mysite www/yoursite www/anothersite
etc
Each site requires the standard web server mappings, eg for mysite the home directory would be www/mysite/www and a /farcry (or whatever else you want to call the mapping) to www/farcry_core/admin. For yoursite the home mapping would be www/yousite/www and a /farcry mapping to www/farcry_core/admin. etc etc
That's all there is to it. Getting FarCry running in a shared environment is not difficult. The hosts that I know of offering shared farcry hosting all have one person looking after farcry_core and fourq and this person would be responsible for running updates to the core code bases as well as update scripts required.
As Spike and the others have said, if there is anything in particular that makes hosting in a shared environment particulary difficult please give us the details and between us all I'm sure we can come up with something.
Daemon itself will be offering shared hosting very shortly so then may be a good time to document the process. More on this hosting later.
Hope that helps :)
-Brendan http://farcry.daemon.com.au
ps if there are hosts out there that want to be listed on the website please send me your details as well as a description of what you offer (eg mysql vs mssql, linux vs windows etc) and where you are located.
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
