CFConfig Documentation
  • Introduction
  • The Basics
    • About This Book
    • Authors
    • Overview
    • Getting Started Guide
    • Supported Engines
    • Config Items
  • Using the CLI
    • Installation
    • Usage
    • CommandBox Server Interceptors
      • Server Start
      • Server Stop
    • Command Overview
      • Export Settings
      • Import Settings
      • Transfer Settings
      • Diff Settings
      • Set/View Settings
      • Manage Datasources
      • Manage CF Mappings
      • Manage Caches
      • Manage Mail Servers
      • Manage Event Gateway Configuration
      • Manage Event Gateway Instances
      • Manage Lucee Loggers
      • Manage Scheduled Tasks
    • JSON File Storage
    • Env Var Overrides
  • Using the Services
    • Installation
    • Component Overview
    • API Overview
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. Using the CLI

CommandBox Server Interceptors

PreviousUsageNextServer Start

Last updated 7 years ago

Was this helpful?

The CommandBox CLI module will automatically register several interceptors that listen for server starts and stops. This allows you to automate your configuration without needing to manually load settings.

This functionality only applies to servers that are started in CommandBox. Examples would be using CommandBox for local development, deploying our Docker images or Heroku buildpacks.

You can use the CFConfig commands to manually import/export configuration on 'standard' CF installs, but these automatic interceptors here don't apply.

  • -- Import config automatically when the server starts

  • -- Optionally export config when the server stops

Server Start
Server Stop