ColdFusion per vhosts mappings
This didn't transpire and so now we use the following technique on apache to map the folder in and then lock it down with apache.
In the vhost section add the following:
<Location /farcry/>
Order Deny,Allow
Deny from all
</Location>
Note: it is important that there is no /farcry mapping defined in the CF Administrator or it will override this setting.
What the above does, is to map in the non-web accessible folder, but then locking it down so it cannot be browsed from the web. This seems pointless but CF can still see the files and correctly resolves the paths even though they are secure from the outside world.
This then allows us to version our sites independently - i.e. if we want to upgrade from farcry 5 to 5.1 we can do it one site at a time, instead of having to test them all at once.
Note - Railo already has per vhost mappings which solve the same problem as this. But if you are on CF7 or CF8 then this works a treat.
Cheers, Mark


The reason I say 'this didn't transpire' is that application mappings don't do everything that real mappings do. I.e. they don't work with cfimports - which we use heavily.
Geoff from Daemon gives a good explanation of it: http://blog.daemon.com.au/go/blog-post/application...
So they do work - but not as well as I'd like them to.
Cheers,
Mark