Clean Host

First, just a little “this is WHY we do this” (and only a little, I promise!).  Everyone seems to get a touch freaked out when going over the FarCry install and its various mappings.  The thing to keep in mind is that the mappings and folder structure exist because FarCry relies heavily upon CFCs and extension of these CFCs.  Even your site, eg. “Project”, relies upon being able to map to these CFCs in a preordained fashion.  The easiest way to pull this off is to have everything reside inside the main FarCry root.

Now, that was the 3.0 and lower builds.  FarCry 4.0 introduced the ability to have the “Project” folder reside completely separately from the FarCry core.  Or, at least that’s my understanding from the new features document.  I’ve not tried this with 3.x (but I do have another method for that!)  Anyway, if this is done, you must make sure that you create a CF mapping to these files in a way that FarCry can reach them.  Since FarCry assumes that the “Project” folder resides in the FarCry root, you need to make a CF mapping that imitates that.  Thus, you need to make the normal CF mapping for FarCry (something like /farcry c:\farcry40) and a mapping to your site, pre-pending farcry to it (/farcry/somesite c:\websites\somesite).  This mapping MUST match what you called the site when installing FarCry.  So, a call to farcry.somesite.whatever will work correctly.  All is good with the universe.

So let’s do an example of this for FarCry 4.0 and the linux shared host out on the interweb using Plesk. 

1. Upload FarCry (and all of it’s supporting libraries farcry_core, fourq, farcry_lib) to one of your domains httpdocs directory.  Doesn’t matter which, really.  One you know will not be deleted.  Ever.
   eg /home/httpd/vhosts/mainsite.com/httpdocs/farcry40
2. Ask the CF admin of your box to create a CF mapping like:
   /farcry /home/httpd/vhosts/mainsite.com/httpdocs/farcry40
3. Upload the mollio template (renamed to somesite) to the domain that will be hosting a FarCry site:
   /home/httpd/vhosts/somesite.com/httpdocs/somesite
4. Ask the CF admin of your box to create a CF mapping like:
   /farcry/somesite /home/httpd/vhosts/somesite.com/httpdocs/somesite
5. Now, this is really, REALLY handy.  Ask the CF admin to create a vhost.conf file for your somesite domain.  This file will never be over written by Plesk and can be used to override the values Plesk sets.  The file should contain:
   DocumentRoot "/home/httpd/vhosts/somesite.com/httpdocs/somesite/www"
   Alias /farcry /home/httdp/vhost/mainsite.com/httpdocs/farcry40/farcry_core/admin
6. Create a database to hold your FarCry information, and ask the CF admin to create DSN pointing to this database
7. Once Plesk gets restarted, browse to www.somesite.com/install and fill in the values as required.  App name in this case is “somesite”, and the project web mapping and farcry web mapping should not be changed.  Click install once all fields are complete
8. Repeat per domain as necessary. Make sure everyone and every group can write into the FarCry plp and tmp directories.

Now let’s do an example of this for FarCry 3.1 and the linux shared host out on the interweb using Plesk

1. Upload FarCry (and all of it’s supporting libraries farcry_core, fourq) to one of your domains httpdocs directory.  Doesn’t matter which, really.  One you know will not be deleted.  Ever.
   eg /home/httpd/vhosts/mainsite.com/httpdocs/farcry31
2. Ask the CF admin of your box to create a CF mapping like:
   /farcry /home/httpd/vhosts/mainsite.com/httpdocs/farcry31
3. Upload the mollio template (renamed to somesite) to the farcry31 directory:
   /home/httpd/vhosts/mainsite.com/httpdocs/farcry31/somesite
4. Now, this is really, REALLY handy.  Ask the CF admin to create a vhost.conf file for your somesite domain.  This file will never be over written by Plesk and can be used to override the values Plesk sets.  The file should contain:
   DocumentRoot "/home/httpd/vhosts/mainsite.com/httpdocs/farcry31/somesite/www"
   Alias /farcry /home/httdp/vhost/mainsite.com/httpdocs/farcry31/farcry_core/admin
5. Create a database to hold your FarCry information, and ask the CF admin to create DSN pointing to this database
6. Once Plesk gets restarted, browse to www.somesite.com/farcry/install and fill in the values as required.  App name in this case is “somesite”, and the project web mapping and farcry web mapping should not be changed.  Click install once all fields are complete
7. Repeat per domain as necessary.  Make sure everyone and every group can write into the FarCry plp and tmp directories.  Make sure everyone and every group can read farcry directories.

The end! I much prefer the first method since it means each domain has its own files reside within the normal directory struture. Much more secure, much easier to manage. Better all around.