> For the complete documentation index, see [llms.txt](https://hollow-peak.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hollow-peak.gitbook.io/docs/getting-started/package-contents.md).

# Package Contents

What is inside the download, and what each folder is for.

```
hollowpeak-commercial/
├── application/            ← the Laravel application — upload this
├── documentation/          offline documentation and screenshots
├── legal/                  licence, terms, privacy template, security, support
├── README.md
├── INSTALLATION.md
├── PRODUCT-OVERVIEW.md
├── CHANGELOG.md
└── VERSION
```

**Only `application/` goes on your server.** The rest is for you.

## Inside `application/`

| Directory      | What it is                                                           |
| -------------- | -------------------------------------------------------------------- |
| `app/`         | Application code — models, controllers, services, payment gateways   |
| `bootstrap/`   | Framework bootstrap and cache                                        |
| `config/`      | Configuration files                                                  |
| `database/`    | Migrations and seeders                                               |
| `public/`      | **The only web-facing directory.** Front controller, CSS, JS, images |
| `resources/`   | Blade templates, source CSS and JavaScript                           |
| `routes/`      | Route definitions                                                    |
| `scripts/`     | Build utilities for regenerating icon sets                           |
| `storage/`     | Uploads, logs, cache, compiled views                                 |
| `tests/`       | The automated test suite                                             |
| `vendor/`      | PHP dependencies, already installed                                  |
| `.env.example` | Configuration template — copy this to `.env`                         |

## Files that matter most

**`.env`** — does not exist until you create it from `.env.example`. Holds your database password and application key. Must never be reachable from the web.

**`public/index.php`** — the front controller. Every request enters here.

**`storage/`** — must be writable by the web server. Holds uploads, logs and compiled templates.

## What is deliberately absent

* **No `.env`** — you create it, so no credentials ship with the package
* **No database dump** — the schema is built by migrations
* **No `node_modules`** — not needed; assets are compiled
* **No `.git`** — no development history
* **No default administrator account** — you create it during installation

## Package size

Roughly 93 MB, most of which is `vendor/`. Uploading a zip and extracting it on the server is far faster than transferring thousands of files over FTP.


---

# 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://hollow-peak.gitbook.io/docs/getting-started/package-contents.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.
