The first entry in my FarCry series will discuss how we set up a custom installation of FarCry, or more specifically, our site.
First, a little background. We followed the install instructions here, however, something about the default directory structure didn’t sit well with us. The one big issue is that, by default, all your ‘projects’ or sites that will use FarCry, are stored in a directory under the main FarCry directory. What we didn’t like about this is that it makes it difficult to seperate out your FarCry code base and your projects into subversion repos. In my specific case, I had personal FarCry sites I am working on using the same FarCry code base, which made it even more difficult to seperate out the code into different repos.
The solution to this issue was actaully quite simple, however, it does require another ColdFusion mapping. In the default installation, you need to create a ColdFusion mapping named ‘farcry’ pointing to the main FarCry directory. In this installation, FarCry expects that your project, let’s say the project is called ‘farcryTest’, will exist in the directory /farCry/projects/farcryTest. The way around the issues outlined above is to move your project into its own directory and create a ColdFusion mapping named ‘/farcry/projects/farCrytest‘ and point it to you project’s main folder. That may look strange, but ColdFusion allows you to create mappings this way. This allowed us to get around the ‘dependancy’ of having your projects stored inside the FarCry directory.
Most people might not have a need for this type of installation, but we may have more than one FarCry site running on the same server. This allows us to easily manage each project (site), as well as maintain the FarCry code base seperately from each other.