> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/reference/deployment/other-engines.md). # Adobe & Lucee Deploy ColdBox on Adobe ColdFusion and Lucee — WAR files, CommandBox servers, and engine-specific notes. ColdBox fully supports both CFML engines. **BoxLang is the preferred runtime** — see [BoxLang Runtimes](/reference/deployment/boxlang-runtimes.md) — but existing Adobe and Lucee estates run ColdBox 8 without changes. ## Adobe ColdFusion Requires **ColdFusion 2023 or newer** (CF 2021 support was dropped in ColdBox 8). ### CommandBox (recommended) ```bash box server start cfengine=adobe@2023 ``` CommandBox manages the engine, JVM, and web server for you — keep `server.json` in source control so production mirrors development. ### WAR / J2EE deployment Install ColdBox into your application (`box install coldbox`) and package the app directory as a WAR through your standard Adobe CF admin or build pipeline. Ensure the engine mappings resolve your `coldbox` folder or configure a per-application mapping. ### Adobe notes * Keep the engine fully patched — several ColdBox guards exist for engine quirks fixed in later updates * Java settings (heap, GC) matter: tune in the CF admin or `jvm.config` * Session scope behavior differs subtly from BoxLang — enable robust session config in the CF admin ## Lucee Requires **Lucee 5+**; Lucee 6/7 recommended. ### CommandBox (recommended) ```bash box server start cfengine=lucee@6 ``` ### WAR deployment Drop the app into a Lucee web context or build a WAR. Lucee's per-web-context mappings make the `coldbox` mapping straightforward — see your `Application.cfc`/`this.mappings` configuration. ### Lucee notes * Null support behavior differs from BoxLang — test thoroughly if enabling full null support * The Lucee admin's datasource and cache definitions can back CacheBox providers directly ## Shared Production Checklist Whatever the engine: * [ ] `debugMode = false` in production * [ ] `reinitPassword` set and secret * [ ] Secrets in `.env`, never in source control * [ ] Handler/event/view caching enabled * [ ] Real CacheBox caches configured * [ ] Health route wired to your monitor * [ ] Scheduled tasks use `onOneServer()` on multi-instance deployments * [ ] HTTPS enforced at the edge Full details: [Deployment Overview](/reference/deployment.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://coldbox.ortusbooks.com/reference/deployment/other-engines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.