BoxLang 🚀 A New JVM Dynamic Language Learn More...

Default ColdBox App Template For BoxLang

v8.2.0+7 MVC

🚀 ColdBox 8 BoxLang Application Template

Welcome to the modern ColdBox 8 BoxLang application template! 🎉 This template provides a solid foundation for building enterprise-grade HMVC (Hierarchical Model-View-Controller) web applications using the BoxLang runtime. Perfect for developers looking to leverage the power of ColdBox with the performance and modern features of BoxLang.

⚙️ Requirements

Before getting started, ensure you have the following installed on your operating system:

BoxLang OS - Operating System Binary
- 📥 Installation: https://boxlang.ortusbooks.com/getting-started/installation
- 📌 Minimum Version: 1.0+
- 🎯 Used for: running BoxLang CLI applications and scripts at the operating system level
CommandBox - CLI toolchain, package manager, and server runtime
- 📥 Installation: https://commandbox.ortusbooks.com/setup/installation
- 📌 Minimum Version: 6.0+
- 🎯 Used for: dependency management, server starting, testing, and task automation
Maven - Java dependency manager (Optional, only if you need Java dependencies)
- 📥 Installation: https://maven.apache.org/install.html
- 📌 Minimum Version: 3.6+
- 🎯 Used for: managing Java dependencies if your project requires them

⚡ Quick Installation

In order to work with this template, you need to have CommandBox and the BoxLang operating system runtime installed on your machine. CommandBox is the application server of choice for BoxLang applications. Please note that running BoxLang web applications is different than the BoxLang OS runtime. The BoxLang OS runtime is used to run BoxLang scripts and command line applications, while CommandBox is used to run web applications.

# Create a new ColdBox application using this BoxLang template
box coldbox create app --boxlang
# Start up the web server
box server start

Your application will be available at http://localhost:8080 🌐

Code to your liking and enjoy! 🎊

⚡ Vite Frontend Build System

If you chose to use Vite during setup, this template includes a modern frontend build system with Vue 3 and Tailwind CSS support. Vite provides lightning-fast hot module replacement (HMR) and optimized production builds.

📂 Asset Structure:

resources/
└── assets/
    ├── css/
    │   └── app.css          # Main stylesheet (Tailwind)
    └── js/
        └── app.js           # Main JavaScript (Vue 3 app)

public/
└── includes/                # Compiled assets (generated by Vite)
    ├── manifest.json        # Asset manifest for production
    └── assets/
        ├── app-[hash].css   # Compiled & hashed CSS
        └── app-[hash].js    # Compiled & hashed JS

🚀 Using Vite

Development Mode (Hot Module Replacement)

npm run dev

This starts the Vite development server with HMR at http://localhost:5173. The ColdBox application automatically detects the dev server and loads assets from it.

Production Build

npm run build

Compiles and optimizes assets for production, outputting them to public/includes/. The generated files include content hashes for cache busting.

📝 Including Assets in Views

The vite() helper function automatically loads assets based on the environment:

<!--- In your Main.bxm layout --->
<head>
    <meta charset="utf-8">
    <meta name="viewport" content="width=device-width, initial-scale=1">
    #vite([
        "resources/assets/css/app.css",
        "resources/assets/js/app.js"
    ])#
</head>

Development: Loads from Vite dev server (http://localhost:5173) Production: Loads compiled assets from public/includes/assets/

🎨 Customizing Vite

Change Output Directory

coldbox({
    input: [ "resources/assets/css/app.css", "resources/assets/js/app.js" ],
    refresh: true,
    publicDirectory: "public",
    buildDirectory: "dist"      // Assets output to public/dist/
})

Add More Entry Points:

coldbox({
    input: [
        "resources/assets/css/app.css",
        "resources/assets/js/app.js",
        "resources/assets/js/admin.js",     // Additional JS entry
        "resources/assets/css/admin.css"    // Additional CSS entry
    ],
    refresh: true
})

Configure Refresh Paths:

coldbox({
    input: [ "resources/assets/css/app.css", "resources/assets/js/app.js" ],
    refresh: [
        "app/layouts/**",
        "app/views/**",
        "app/config/Router.bx",
        "app/handlers/**/*.bx"   // Also refresh on handler changes
    ]
})

📚 Learn More: Check out the coldbox-vite-plugin documentation and Vite documentation for advanced configuration options.

📦 Build Script (`Build.bx`)

The Build.bx script compiles and packages your application for distribution. It creates optimized, production-ready builds that can be deployed to any environment.

boxlang Build.bx

What Build.bx Does:

The build process performs the following steps:

🧹 Clean Build Directory: Removes any existing build/ folder and creates a fresh structure
📁 Copy Sources: Copies application files (app/, modules/, public/, runtime/) to the build package
⊘ Smart Exclusions: Automatically excludes:
- Log files and directories (logs/, *.log)
- System files (.DS_Store, Thumbs.db)
- Hidden files and folders (.git, .gitignore, etc.)
🏷️ Build ID: Creates a build information file with project name, version, and timestamp
🔨 Compilation: Compiles BoxLang sources in app/ and public/ to optimized bytecode
📦 Distribution Package: Creates a ZIP file: build/distributions/{projectName}-{projectVersion}.zip
🔐 Checksums: Generates security checksums (MD5, SHA-256, SHA-512) for integrity verification

Build Output Structure:

build/
├── package/                          # Staged files ready for distribution
│   ├── app/                         # Compiled application code
│   ├── modules/                     # Application modules
│   ├── public/                      # Compiled public assets
│   ├── runtime/                     # Runtime configuration (without logs)
│   └── {projectName}-{version}.md   # Build information
└── distributions/                    # Final distribution files
    ├── {projectName}-{version}.zip
    ├── {projectName}-{version}.zip.md5
    ├── {projectName}-{version}.zip.sha256
    └── {projectName}-{version}.zip.sha512

Customizing the Build:

You can customize what gets included or excluded by editing the Build.bx file's initialization section. The build script uses two configurable arrays:

📦 Sources Array - What to Include

Controls which directories and files get packaged in your distribution:

// Source directories to package
variables.sources = [
    ".cbmigrations.json",  // Database migrations state
    "box.json",            // Project metadata
    "app",                 // Your ColdBox application
    "modules",             // Installed modules
    "public",              // Web root with assets
    "runtime"              // BoxLang runtime config
];

To add more sources, simply append to the array:

variables.sources = [
    ".cbmigrations.json",
    "box.json",
    "app",
    "modules",
    "public",
    "runtime",
    "config",              // Add custom config directory
    "resources/database"   // Include database resources
];

🚫 Excludes Array - What to Skip

Uses regex patterns to exclude files/directories from the build:

// Files and folders to exclude from the build (regex patterns)
variables.excludes = [
    "logs/",           // Log directories
    "\.DS_Store$",     // macOS system files
    "Thumbs\.db$"      // Windows system files
];

Common exclusion patterns:

variables.excludes = [
    "logs/",              // Exclude all log directories
    "\.log$",             // Exclude .log files
    "\.tmp$",             // Exclude .tmp files
    "test-results/",      // Exclude test output
    "node_modules/",      // Exclude npm dependencies
    "\.git",              // Exclude git repository
    "\.env",              // Exclude environment files
    "\.bak$",             // Exclude backup files
    "resources/vite/",    // Exclude vite resources after setup
    "resources/rest/"     // Exclude rest resources after setup
];

Regex Pattern Tips:

Use $ to match end of string: \.log$ matches files ending in .log
Use / to match directories: logs/ matches any logs directory
Use \. to escape dots: \.DS_Store$ matches .DS_Store files
Use .* for wildcards: temp.* matches anything starting with temp

🔧 Example: Custom Build Configuration

function init(){
    // ... existing code ...

    // Custom sources for your project
    variables.sources = [
        ".cbmigrations.json",
        "box.json",
        "app",
        "modules",
        "public",
        "runtime",
        "custom-config",        // Add your custom directory
        "static-files"          // Add static file directory
    ];

    // Comprehensive exclusions
    variables.excludes = [
        "logs/",                // No log files
        "\.DS_Store$",          // No macOS files
        "Thumbs\.db$",          // No Windows files
        "test-results/",        // No test outputs
        "\.env\..*",            // No environment files
        "resources/vite/",      // No vite setup resources
        "resources/rest/",      // No rest setup resources
        "resources/docker/",    // No docker setup resources
        "Setup\.bx$"            // No setup script
    ];

    return this;
}

💡 Pro Tip: Review your variables.excludes after running Setup.bx to ensure you're not packaging unnecessary setup resources!

Deploying Your Build:

Once the build completes, you can:

Upload the ZIP: Deploy {projectName}-{version}.zip to your server
Verify Integrity: Use the checksum files to verify the package wasn't corrupted during transfer
Extract & Run: Unzip on your server and start with CommandBox

# On your server
unzip cbtemplate-boxlang-1.1.0.zip
cd cbtemplate-boxlang-1.1.0
box server start

🚀 Pro Tip: Integrate Build.bx into your CI/CD pipeline to automatically build and deploy your application on every release!

📁Application Structure

This ColdBox 8 application follows a clean, modern architecture with the following structure:

🏗️ ColdBox Application (`/app/`)

This folder contains the main ColdBox application code via conventions, including configuration files, event handlers, models, views, and more. This is where you will be coding most of your application logic.

app/
├── 🔧 config/                # Configuration files (Optional)
│   ├── CacheBox.bx           # Caching configuration
│   ├── ColdBox.bx            # Main framework settings
│   ├── Router.bx             # URL routing definitions
│   ├── Scheduler.bx          # Task scheduling
│   └── WireBox.bx            # Dependency injection
├── 🎮 handlers/              # Event handlers (controllers)
├── 🛠️ helpers/               # Application helpers (Optional)
├── 🎨 layouts/               # View layouts
├── 📝 logs/                  # ColdBox logs (Optional)
├── 🏗️ models/                # Business logic models
├── 📦 modules_app/           # Application-specific modules (Optional)
└── 👁️ views/                 # View templates

🌐 Public Web Root (`/public/`)

This folder contains all the publicly accessible assets and the main application entry point. The CommandBox or MiniServer or Whatever server will point to this folder as the web root.

public/
├── 📱 Application.bx         # Web-facing application Bootstrap
├── 🎯 index.bxm              # Main entry point (Empty)
├── 🖼️ favicon.ico            # Site icon
├── 🤖 robots.txt             # Search engine directives
└── 📦 includes/              # CSS, JS, images or any resources you want

🔧 Configuration & Build

This folder contains configuration files, dependencies, Docker setup, and runtime environment.

├── 📋 box.json               # CommandBox dependencies and project descriptor
├── 🏗️ pom.xml                # Maven dependencies (Optional)
├── 🖥️ server.json            # CommandBox Server configuration
├── 🐳 docker/                # Docker configuration (Optional)
├── 🧪 tests/                 # Test suites (NOT OPTIONAL)
├── 📦 modules/               # ColdBox application modules (Managed by CommandBox)
├── ⚙️ runtime/               # BoxLang runtime environment overrides and resources
│   ├── 🔧 boxlang.json               # Custom BoxLang configuration overrides
│   ├── global/               # Global classes and BoxLang components (Optional)
│   │   ├── classes/          # Global BoxLang classes
│   │   └── components/       # Global BoxLang components
│   ├── lib/                  # Runtime libraries (Managed by Maven/CommandBox)
│   ├── logs/                 # BoxLang logs
└── 📚 resources/             # ColdBox/CommandBox module resources
    ├── migrations/           # Database migrations (cbmigrations)
    ├── seeders/              # Database seeders
    ├── swagger/              # API documentation (cbswagger)
    └── other module assets/  # Various module-specific resources

🗺️ BoxLang Mappings

This template comes pre-configured with essential BoxLang mappings in the runtime/config/boxlang.json file to make development seamless. These mappings provide convenient shortcuts to access different parts of your application:

📍 Core Application Mappings

"/public": "${user-dir}/public",           // Public web root
"/app": "${user-dir}/app",                 // ColdBox application
"/tests": "${user-dir}/tests",         // Test suites (Can be removed for production)

🏗️ Framework & Library Mappings

"/coldbox": "${user-dir}/runtime/lib/coldbox",              // ColdBox framework
"/coldbox/system/exceptions": "...coldbox/system/exceptions", // ColdBox exceptions (external)
"/testbox": "${user-dir}/runtime/lib/testbox"               // TestBox testing framework

📦 Module Mappings

"/modules": "${user-dir}/modules"    // Application modules directory

🔧 External vs Internal Mappings

External mappings ("external": true) - Can be accessed via web requests and file resolution
Internal mappings ("external": false) - Only accessible programmatically, not via web requests

This mapping structure ensures your ColdBox application has clean, predictable paths for all its components while maintaining security by controlling web accessibility! 🛡️

☕ Java Dependencies

If your project relies on Java third-party dependencies, you can use the included Maven pom.xml file in the root. You can add your dependencies there and then run the mvn install command to download them into the runtime/lib folder. The BoxLang application will automatically class load all the jars in that folder for you! 🎯

You can also use the mvn clean command to remove all the jars. 🧹

You can find Java dependencies here: https://central.sonatype.com/. Just grab the Maven coordinates and add them to your pom.xml file. 📦

🐳 Dockerfile

We have included a docker/Dockerfile so you can build docker containers from your source code. We have also added two scripts in your box.json so you can build the docker image and run the docker image using our CommandBox Docker containers.

# Build a docker **container**
run-script docker:build
# Run the container
run-script docker:run
# Go into the container's bash prompt
run-script docker:bash

🐙 Docker Compose Stack

We have included a docker/docker-compose.yaml stack that can be used to run the application in a container alongside a database. We have included support for MySQL, PostgreSQL and MSSQL. We have also included the run-script docker:stack command you so you compose the stack up or down.

run-script docker:stack up
run-script docker:stack down

💻 VSCode Helpers

We have included two vscode helpers for you:

.vscode/settings.json - Includes introspection helpers for ColdBox and TestBox 🔍
.vscode/tasks.json - Tasks to assist in running a Test Bundle and a CommandBox Task ⚡

We have included two custom tasks:

Run CommandBox Task - Open a CommandBox task and run it 🏃‍♂️
Run TestBox Bundle - Open the bundle you want to test and then run it 🧪

To run the custom tasks open the command palette and choose Tasks: Run Build Task or the shortcut ⇧⌘B 🚀

🎉 Welcome to ColdBox

ColdBox Hierarchical MVC is the de-facto enterprise-level HMVC framework for BoxLang and CFML developers. It's professionally backed, conventions-based, modular, highly extensible, and productive. Getting started with ColdBox is quick and painless. ColdBox takes the pain out of development by giving you a standardized methodology for development with features such as:

📐 Conventions instead of configuration
🛣️ Modern URL routing
🚀 RESTFul APIs
🏗️ A hierarchical approach to MVC using ColdBox Modules
🎯 Event-driven programming
⚡ Async and Parallel programming constructs
🧪 Integration & Unit Testing
💉 Included dependency injection
🗄️ Caching engine and API
📝 Logging engine
🌐 An extensive eco-system
🎊 Much More

📚 Learning ColdBox

ColdBox is the defacto standard for building modern BoxLang and ColdFusion (CFML) applications. It has the most extensive documentation of all modern web application frameworks. 📖

If you don't like reading so much, then you can try our video learning platform: CFCasts (www.cfcasts.com) 🎥

💰 ColdBox Sponsors

ColdBox is a professional open-source project and it is completely funded by the community and Ortus Solutions, Corp. Ortus Patreons get many benefits like a cfcasts account, a FORGEBOX Pro account and so much more. If you are interested in becoming a sponsor, please visit our patronage page: https://patreon.com/ortussolutions ❤️

🙏 THE DAILY BREAD

"I am the way, and the truth, and the life; no one comes to the Father, but by me (JESUS)" Jn 14:1-12

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Unreleased

8.2.0 - 2025-10-10

8.1.1 - 2025-10-10

Fixed

ColdBox.bx syntax update

8.1.0 - 2025-10-10

8.0.0 - 2025-10-10

Added

ColdBox 8 readyness

1.1.0 - 2025-06-07

1.0.0 - 2025-04-29

First creation of the changelog file.

Ortus Solutions
Published
8.2.0+7 is the latest of 9 release(s)
Published
Published on {{ getFullDate("2025-10-10T14:37:01Z") }}

$ box install cbtemplate-boxlang

How do I do this?

No collaborators yet.

Default ColdBox App Template For BoxLang
Created On: {{ getFullDate("2025-10-08T11:43:27Z") }}
Last Publish: {{ getFullDate("2025-10-10T14:37:01Z") }}
Views: 48
Installs: 40

Report Abuse