Our install is dead-standard FarCry out of the box. The admin files are all on the file server that the web servers connect to. There are no FarCry files on any webserver.
On that fileserver we just have an install with the core FarCry files, the FourQ directory, and however many directories we need for each FarCry application. Standard FarCry directory structure. The FarCry directory (or it's root in fact) is shared out as a standard drive letter. On each webserver, we then set up the appropriate mappings as if that server was the only one connected. To alleviate any issues with Session variables, the load balancer is configured to run with sticky sessions (i.e. subsequent calls within a specified session period return the use to the same server). The only interruption to this is if we decide to take a server out of the farm (either via the load balancer or by manipulating the machine in some way). Make sense ? Gary On Fri, 11 Mar 2005 04:46:35 +1100, Tom Barr <[EMAIL PROTECTED]> wrote: > Gary, > All of that is very helpful, especially the updateapp technique. > > Do you deploy the complete core file directory? My ultimate question is: > is admin/index.cfm and associated files on all production servers? If not > how is separated out from the rest of the FarCry application? > > Thanks. > > --- > You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] > To unsubscribe send a blank email to [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to farcry-dev as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
