Galleon Forum Ports Comparisons

Application Settings

back

Development Modes: Most frameworks cache some of their settings for performance reasons, however, during development the changes to the software need to be reflected immediately (i.e. no caching), so in general frameworks will also include a setting indicating a production or development mode in which the caching it turned on or off respectively. Some frameworks also include a setting to turn on or off custom debug output for the framework at the end of the request, similar to the native debug output in ColdFusion with information specific to the framework.

• ColdBox: /config/coldbox.xml.cfm
• <Setting name="HandlersIndexAutoReload" value="true or false" />
• <Setting name="ConfigAutoReload" value="true or false" />
• <Setting name="HandlerCaching" value="true or false" />
• <Setting name="DebugMode" value="true or false" />
• DEPRECATED: <DevEnvironments><url>localhost</url></DevEnvironments>
• Fusebox 5: /fusebox.xml.cfm
• <parameter name="mode" value="...">
• development-circuit-load : caches the fusebox.xml config file - thread safe
• development-full-load : no caching - not thread safe (problematic with AJAX or a shared dev environment)
• production : caches the fusebox.xml config and all circuit.xml config files
• <parameter name="debug" value="true or false">
• Mach-II: MACHII_CONFIG_MODE = ... (Application.cfc)
• 1 = development - always reloads the framework
• 0 = dynamic - reloads XML files if they've been modified
• -1 = production - caches everything
• Model-Glue: /config/ColdSpring.xml
• <property name="reload"><value>true or false</value></property>
• <property name="rescaffold"><value>true or false</value></property> (optional)
• <property name="debug"><value>true or false</value></property>
• onTap: /_components/_appsettings.cfm (debug can be set anywhere)
• request.tap.development = true or false (true causes onApplicationStart to execute on each request)
• request.tap.cf.onrequestend.debug = true or false

Reinit: Along with development and production modes, frameworks also generally include a method of reinitializing the framework via url irrespective of its operating mode. So for example, you might have a production server at http://www.widgetworld.com and you could force the appolication to reload by adding ?init=true to the URL.

• ColdBox: index.cfm?fwreinit=[true or password] (password is required if set in the config xml)
• Fusebox 5:
• reload all: index.cfm?fusebox.load=true
• reload circuit: index.cfm?fusebox.parse=true&[fuseaction]=app.fuseaction
• &fusebox.password=[password] (required according to the documentation - defaults to an empty string - set in fusebox.xml parameters)
• Mach-II: not implemented - the dev team plan to implement a "dashboard" with the ability to restart applications among other things - I found reference to the plan in mid April 2008 on the Mach-II google group, but don't know the status
• Model-Glue: index.cfm?[reloadKey]=[reloadPassword] (reloadKey and reloadPassword are properties in the ColdSpring.xml config - defaults to init=true)
• onTap: code it yourself in /_components/_appsettings.cfm using the request.tap.development property