ColdBox HMVC Documentation
Master ClassVideo TrainingCommunitySupport
Search…
6.x
Introduction
Intro
Release History
About This Book
Author
For Newbies
60 Minute Quick Start
Getting Started
Getting Started Guide
Installation
Conventions
Configuration
The Basics
Request Context
Routing
Event Handlers
Layouts & Views
Models
Interceptors
HMVC
Modules
Core Modules
Locations
Parent Configuration
Module Layout
Module Service
ModuleConfig
Module Event Executions
URL Routing
Module Async Scheduling
Request Context Module Methods
Layout and View Renderings
Models
Module CF Mappings
Module Dependencies
Module Helpers
Module Bundles
Module Inception
Testing
Testing Quick Start
Testing ColdBox Applications
Digging Deeper
Async Programming
ColdBox Proxy
Controller Decorator
Flash RAM
HTML Helper
REST Handler
Request Context Decorator
Recipes
Scheduled Tasks
Architecture Concepts
What is MVC
What is ColdBox
How ColdBox Works
Testing Concepts
External links
Source code
Issue tracker
LogBox
CacheBox
WireBox
Powered By GitBook
Parent Configuration
There are a few parent application settings when dealing with modules. In your ColdBox.cfc you can have a modules structure with some configuration settings.
1
modules = {
2
// reload and unload modules in every request
3
// DEPRECATED in coldbox 5
4
autoReload = false,
5
// An array or list of the module names that will load ONLY
6
include = [],
7
// An array or list of the module names that will be EXCLUDED
8
exclude = ["paidModule1","paidModule2"]
9
};
Copied!
Previous
Locations
Next
Module Layout
Last modified 2yr ago
Copy link
Edit on GitHub