./core/admin has been renamed to ./core/webtop in a bid to clarify the intent of these areas of the code base. Having made these changes now, we're hoping this will not put any additional burden on developers above changes required to accommodate the implementation of Application.cfc

Target Deployment Configurations

With the release of Fortress there will be several recommended deployment options. Given the flexibility of the environment many other configurations are possible, however, they will not be specifically tested for. These deployment options will be fully supported in the Fortress installer.

Standalone

Default installer configuration option.

Specifically aimed at one application per website. For standalone application deployment and/or shared hosting deployment that allows for a single project with a dedicated core framework and dedicated library of plugins.

In this example, the contents of c:\hostapps\myproject\farcry\projects\myproject\www is copied into c:\hostapps\myproject and the directory renamed to c:\hostapps\myproject\farcry\projects\myproject\wwwCopiedToWebroot

Optional: Remapping /farcry/core/webtop The standalone configuration will default to users needing to reference the webtop via /farcry/core/webtop. If you want to change this to something else, for example, abbreviating to /webtop you will need to make a couple of configuration changes. Firstly, you'll need a web virtual (we'll assume you can handle this yourself). Then you will need to update the application.url.farcry to reference your new mapping, such as "/webtop", in your project's ./config/serverSpecificVars.cfm file. application.url.farcry is a global constant that maps functionality under the webtop via a reference relative to the webroot of your project.

Sub-Directory

Recommended for local development only.

For multiple application deployment under a single webroot. Specifically aimed at one multiple applications per website.

In this example, c:\hostapps\myproject\farcry\projects\myproject\www is moved or copied to c:\hostapps\webroot\myproject

Advanced Configuration (ColdFusion Mapping)

Current best practice for 4.0.x is to use a CF mapping. Will be considered an advanced deployment option from Fortress onwards.

This installation configuration is not suitable for projects running in a shared hosting environment.

An enterprise configuration that allows for an unlimited number of projects to share a single core framework and library of plugins. Sharing is done through common reference to specific ColdFusion mapping of /farcry.

Advanced Configuration (Webserver Mapping)

New for Fortress. Considered an advanced deployment option similar to ColdFusion mapping.

An enterprise configuration that allows for an unlimited number of projects to share a single core framework and library of plugins. Sharing is done through common reference to specific web server mapping (aka web virtual directory) of /farcry.