> For the complete documentation index, see [llms.txt](https://logbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://logbox.ortusbooks.com/2.x/getting-started/installation.md).

# Installation

LogBox can be downloaded as a standalone framework or it is included with the latest ColdBox Platform release. The main difference between both versions is the instantiation and usage namespace, the rest is the same.

The best way to install LogBox is using **CommandBox CLI and package manager**.

* [Download LogBox Standalone](https://www.coldbox.org/download)
* [API Docs](https://apidocs.ortussolutions.com/logbox/5.0.0/index.html)

## System Requirements

* ColdFusion 11+
* Lucee 4.5+

## Manual Installation

If you are using LogBox within a ColdBox application context, then LogBox is part of the platform. Just install ColdBox normally. If you are using LogBox standalone, just drop LogBox in your application root or create a mapping called `logbox` that points to the installation folder. If you can run the following snippet, then LogBox is installed correctly:

```java
logbox = new logbox.system.logging.LogBox();
```

## CommandBox Installation

You can leverage [CommandBox](http://www.ortussolutions.com/products/commandbox) to install the standalone version of LogBox

```bash
# Latest CommandBox
box install logbox

# Bleeding Edge
box install logbox@be
```

## Namespaces

**Standalone**

`logbox.system.logging`

**ColdBox**

`coldbox.system.logging`

> **Info** In this book we will be using the standalone namespace for all examples.

## Useful Resources

* [LogBox Docs Source](https://github.com/coldbox/logbox-docs)
* [LogBox Planning Board](https://ortussolutions.atlassian.net/browse/LOGBOX)
* [Log4J](http://logging.apache.org/log4j/2.x/)
* [LogStash](http://logstash.net)


---

# 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://logbox.ortusbooks.com/2.x/getting-started/installation.md?ask=<question>&goal=<user_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.