> For the complete documentation index, see [llms.txt](https://cloud-servers.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloud-servers.ortusbooks.com/aws/windows-based-images/other-engines/contentbox-5/running-contentbox.md).

# Running Contentbox

This page will explain the necessary sites to run Contentbox 5 on your AWS Cloud site. Let's take care of some homework first. The GUI part of the Lucee admin is disabled on Contentbox 5. \
\
The sites are at:\
C:\inetpub\wwwroot\site1 | C:\inetpub\wwwroot\site2\
Commandbox is at C:\box\
\
All Lucee admin functionality can be ministered maintained via the Commandbox module CFConfig. Here is a link to get you started with that. <https://cfconfig.ortusbooks.com/>\
To see your Lucee admin settings open a CLI and open a box shell and run.\
cfconfig show

Now let's get Contentbox configured and running on the demo site. If you are an experienced user then create your own site. Here are the steps to get that first site running.

1. Open a browser and if you have not run this [Powershell code](/aws/windows-based-images/other-engines/contentbox-5.md) at the bottom of the page you will need to or do it by hand. Paste this URL into your browser and go. <http://luceesite1.com>

   <figure><img src="/files/Lvx9mvZubWpy9NlsccVX" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Th7ezDCuu0pMHWrUijOu" alt=""><figcaption></figcaption></figure>

* Set the email address

  <figure><img src="/files/92RJaIKbznTbF3vpw5Mc" alt=""><figcaption></figcaption></figure>
* Create the CMS

  <figure><img src="/files/5J5JX6epcA5MEmXNeRBk" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cloud-servers.ortusbooks.com/aws/windows-based-images/other-engines/contentbox-5/running-contentbox.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.