Simon James
b54a3139c7
Includes QWB, Qortal Web, and Q-Shops Q-Apps with shared packages and build scripts. Co-authored-by: Cursor <cursoragent@cursor.com>
13 lines
1.4 KiB
Plaintext
13 lines
1.4 KiB
Plaintext
---
|
|
description: Qortal Q-App is served from published zip on QDN; integrate via qortalRequest only
|
|
alwaysApply: true
|
|
---
|
|
|
|
# Qortal / QDN runtime
|
|
|
|
- The **Q-App** that QDN and the Hub run is the **zip you publish** (build output: `dist/` → e.g. `Qortal-Hub-Dev-Test-*.zip`). That bundle is the **only** app surface QDN is meant to load for this product.
|
|
- The environment is **sandboxed** relative to normal web apps: end-user **blockchain and QDN access** in-app should go through **`qortalRequest`** (see `getQortalRequest()` / `qortalClient`), not custom backends.
|
|
- **Ship** fonts, images, and JS **in the zip**; avoid **hard dependencies on external CDNs** for anything required in Qortal, so the app works offline to the open internet in typical Hub use.
|
|
- A **non-Qortal** “browser / preview” path is for local testing when the API bridge is missing; it is not a replacement for the published Q-App.
|
|
- For deployable work, run **`npm run build`** and use **`npm run zip:hub`** (or `bash scripts/make-zip.sh`) to produce the flat **`dist/`** archive for QDN/Hub (zip **contents** of `dist`, not a wrapper folder). Official Q-App behaviour and **WEBSITE vs APP** routing are documented in [Q-Apps.md](https://github.com/Qortal/qortal/blob/master/Q-Apps.md) and [qortal.dev Q-Apps](https://qortal.dev/docs/q-apps); see **`QORTAL-HUB.md`** in this repo for Hub-specific steps and [github.com/qortal](https://github.com/qortal) for org repos (Hub, qapp-core, examples).
|