An Architect's View

CFML, Clojure, Software Design, Frameworks and more...

An Architect's View

Installing Frameworks via the Railo Administrator

April 17, 2009 ·

One of the neat features of the Railo Administrator console is that you can easily install pre-packaged applications with just a few clicks. As part of my recent presentation comparing application frameworks, I installed ColdBox, ColdSpring, Mach-II and Model-Glue via the Web Administrator. There are a couple of "gotchas" about the current default settings for those installations that I wanted to cover in a blog post.All of the default installation paths contain the version number of the framework and a dash ('-'). This can make it problematic to run the framework sample applications without some additional changes. Here's how to make it easier to get these frameworks up and running: ColdBox ColdBox ships with a rich set of sample applications so it expects that you will, initially, install the framework bundle under your webroot. The easiest way to do this in the Railo Web Administrator is to change the install directory name to just 'coldbox' under the webroot (instead of 'coldbox-2.6.3-1' currently). This allows you to visit http://localhost:8888/coldbox/ in your browser and use the dashboard or view the sample applications. Note: if you wish to take advantage of Railo's per-mapping trusted cache feature, you should leave the option selected to create the mapping during installation and then, after installation, go to Archives & Resources > Mappings and you can just check the Trusted option and save the mappings. ColdSpring ColdSpring also ships with sample applications so, if you want to browse those directly, you'll need to ensure the installation directory has no special characters in it. Just change the install directory name to 'coldspring' under the webroot (instead of 'coldspring-1.2' currently). Mach-II Although Mach-II does not ship with sample applications, you still need to make a change to the defaults during installation. The default mapping is shown as '/Mach-II' so you need to correct that to '/MachII' (without the dash). You can leave the install directory alone (it is 'Mach-II-1.5' currently). Note: the Mach-II website does not seem to have the 1.5 skeleton application available. You can download the 1.6 skeleton and use that with just a couple of changes:
  • In Application.cfc, remove the extends= attribute - that's a new feature introduced in 1.6.
  • In index.cfm, add <cfinclude template="/MachII/mach-ii.cfm"/> (the flip side of the change to Application.cfc).
  • Don't forget to change the application name in mach-ii.xml to match the name of the directory in which you placed the skeleton app!
Model-Glue Model-Glue ships with some sample applications and a new application template. Unlike ColdBox and ColdSpring, the Model-Glue framework itself is inside a subdirectory of the installation package. That means we need to make the following changes during installation:
  • Change the install directory name to 'MG' under the webroot (instead of 'ModelGlue-2.0.34' currently).
  • Leave the mapping alone for installation - we'll change it post-install.
  • Complete the installation.
  • Go to Archives & Resources > Mappings and change the Resource from {webroot}/MG to {webroot}/MG/ModelGlue and save the mappings. You can check the Trusted option before saving, if you wish.
Outside the webroot Of course, if you don't want to install the frameworks under your webroot (and on a production system you would not generally want to), you can change the install directory locations appropriately during installation of each framework. You'll still need to change Mach-II's default mapping to '/MachII' instead of '/Mach-II', and update the '/ModelGlue' mapping to point to the ModelGlue subfolder after installation.

Tags: coldbox · coldfusion · coldspring · machii · modelglue · railo

0 responses