JohnBs personal blog

One of the main reasons I’ve not been blogging all that much about Fusebox for over a year now is because quite simply, I’ve not been using it. Almost all my work has been building sites using our CMS of choice (iCM from Goss interactive) which provides a framework/API to building sites so there has been little need to use Fusebox or indeed any framework. But now I’ve got a growing pile of project specifications for Intranet applications which, despite needing to interface with the intranet can exist as their own entities.

So what’s the problem here? Bearing in mind we’ve got an existing Intranet running in it’s own CF application name with Fusebox4 an application would create a ‘fusebox’ structure in the application scope - all well and good if you’ve only got a single Fusebox application but as soon as you introduce a second Fusebox application then the second Fusebox application will overwrite the first Fusebox application in the application scope. Yes, it was something that could be fixed by ‘tweaking’ the cores but we decided to wait until the cores supported these environments out of the box.

Fusebox 5 now lets you run multiple FB applications without overwriting each other by setting a new variable in your index.cfm;

To confirm this behvaiour I used the Skeleton application (in a folder skeletonA) which just displays how long the application has been running. In the index.cfm supplied with the skeleton application I replaced

with the Fusebox_Application_Key line as above and removed the application.cfm from the folder as the application name was already being set from a parent Application.cfm. I then took a copy of the skeleton folder and named it skeletonB and changed the fusebox_application_key to AppB. So now, hitting either the /skeletonA or /skeletonB showed differing times for how long each application has been running for, and just to be double sure - a cfdump of the application scope shows the two applications living in application.AppA and application.AppB - woooohooo!