> For the complete documentation index, see [llms.txt](https://docs.elevateelysium.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elevateelysium.xyz/running-the-platform/deploy.md).

# Deploy and configure

The full step-by-step is in the repository: `docs/elysium/launchpad-deploy.md` (contract), `docs/deploy-vps.md` (server or your own PC) and `docs/RUNNING.md` (local).

Order of work:

1. Create the server environment from `.env.mainnet.example`. Never commit it.
2. Create a fresh executor key that holds only gas, and fund it.
3. Deploy the launchpad (browser deploy page or script), then set `ELYSIUM_LAUNCHPAD_ADDRESS` and `ELYSIUM_LAUNCHPAD_START_BLOCK`.
4. Run migrations (`scripts/post-merge.sh`; safe to repeat).
5. Open the [operator panel](/running-the-platform/admin-panel.md) and work down the checklist.
6. Optionally deploy Programs and Collectibles, then enable them in the panel.

The full ordered list of owner-only launch steps is in the repository at `docs/LAUNCH-CHECKLIST.md`.

## Where it runs: Cloudflare and Docker

The site is served at **elevateelysium.xyz** through a Cloudflare Tunnel: the machine running the app opens no inbound ports, Cloudflare terminates HTTPS, and the origin is never exposed directly.

* **Domain and DNS:** the domain is on Cloudflare (Full setup). The apex and `www` hostnames route through the tunnel to the web container. This documentation can be served at `docs.elevateelysium.xyz`.
* **Cloudflare settings:** SSL/TLS mode Full (strict), Always Use HTTPS, Automatic HTTPS Rewrites, and a rate-limit rule on `/api/` (the free plan allows a 10-second window, so the rule blocks an IP for 10 seconds after 100 `/api/` requests in 10 seconds). The API keeps its own per-wallet limits as well.
* **Docker:** the same compose files run on a VPS or on a PC with Docker Desktop. A PC works for testing and early use, but the site is only online while the PC is on, awake and running Docker, so a VPS is the safer home before real user funds.
* **One-click start on a PC:** double-click `start.bat` (no arguments; `stop.bat` stops it). It builds the stack with the tunnel, generates the session secret and a strong database password, and asks for the tunnel token in a hidden prompt.
* **Secrets:** the tunnel token and every value in `.env.mainnet` stay on the machine that runs the stack. Never paste them into chat, tickets or the repository.


---

# 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.elevateelysium.xyz/running-the-platform/deploy.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.