This template is a work in progress where we are testing a different approach to ColdBox templates.
Instead of having all files in the web root, this template only puts public files in the web root and thus called public.
If you are using CommandBox, everything should "just work" but if you want to run this behind IIS/Apache, etc you'll need to re-create the web server aliases that are in the server.json.
app- Location of the ColdBox CFML app (Handlers, config, interceptors, views, custom modules, etc.)coldbox- ColdBox libslib- Java libslogs- App and Server logsmodules- CommandBox installed ColdBox modulespublic- Public webroot (UI assets, etc)resources- Migrations, apidocs, UI source assetstestbox- TestBox libstests- Tests
Everything is locked down by default. Any modules you install that require UI assets will require a CommandBox web alias (https://commandbox.ortusbooks.com/embedded-server/configuring-your-server/aliases) that you can provide easily in the server.json. Here are the ones we ship with:
"aliases":{
// We expose the cbdebugger module
"/modules/cbdebugger":"../modules/cbdebugger",
// We expose the ColdBox Exceptions UI
"/coldbox/system/exceptions":"../coldbox/system/exceptions/",
// Expose TestBox for testing purposes
"/testbox":"../testbox/",
// Expose Tests for testing purposes
"/tests":"../tests/"
}Apache License, Version 2.0.
Source Code
Each application templates contains a box.json so it can leverage CommandBox for its dependencies.
Just go into each template directory and type:
box installThis will setup all the needed dependencies for each application template. You can then type:
box server startAnd run the application.
"I am the way, and the truth, and the life; no one comes to the Father, but by me (JESUS)" Jn 14:1-12