> For the complete documentation index, see [llms.txt](https://docs.neoncloud.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neoncloud.com/neon-cloud-marketplace-1-click-apps/business-analytics.md).

# Business Analytics

<details open>

<summary>OpenCart on Ubuntu 22.04</summary>

**Getting Started After Deploying OpenCart:**

After your first SSH login to the VM or launching the VM console (via the 1-Click OpenCart deployment), access the OpenCart web installer by visiting:

```
http://<your-server-ip>/opencart/upload
```

Click "**Continue**" to begin the installation process.

1. **Enter Database Connection Details**\
   When prompted, fill in the following:\
   ⦁ DB Driver: MySQLi\
   ⦁ Hostname: localhost\
   ⦁ Database Username: opencartuser\
   ⦁ Database Password: password!\
   ⦁ Database Name: opencart (assumed; create if not exists)\
   ⦁ Database Prefix: oc\_\
   ⦁ Port: 3306
2. **Set Up Admin Credentials**\
   Create an administrator username and password that you’ll use to manage your OpenCart store.\
   Click "Continue" to finalize the setup.
3. **Access the OpenCart Admin Panel**\
   Once installation is complete, log in to your OpenCart dashboard:

```
http://<your-server-ip>/opencart/admin
```

4. **Use the admin credentials you just created to log in.**

</details>


---

# 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://docs.neoncloud.com/neon-cloud-marketplace-1-click-apps/business-analytics.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.
