Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
2. Connect QHQ and make changes deliberately
QHQ uses authenticated HTTPS APIs. It does not open the cloud's databases or manage Docker directly. This matters when diagnosing a failed Create: the UI can submit a valid request while a missing external helper prevents the resource from becoming ready.
Step 1: connect to the intended instance
Open Emulator → Connection. Enter its HTTPS endpoint, the path to that instance's
bootstrap credentials.json, and the trusted public CA certificate. Connect
and check the tenant/subscription shown under Azure / Entra ID → Tenant. The
credentials file is not an access-token file or an application settings file.
A remote QHQ workstation needs its own securely delivered credential file and
public CA; it does not need the server's TLS private key or CA signing key.
For direct launch, use the following shape, substituting your installation paths:
bin/debug/qhq --endpoint https://localhost:11443 \
--credentials .local/quinzee/credentials.json \
--ca-file .local/certificates/ca/quinzee-dev-root-ca.crt
Step 2: understand selection and scope
Navigation categories start collapsed. Expand the required category and choose
a page. Tab/Shift+Tab move between controls. A Browse list selection determines
what Save selected, Delete selected, Start or Stop will affect. Entering a new
name does not select an existing object. Scope fields use ARM resource IDs such
as /subscriptions/<UUID>; display names are not interchangeable with IDs.
On the identity forms, select a row in Browse, then open Create / Edit. Create makes a new object; Save selected updates the selected one. Refresh replaces inventory and clears selection, so select again before editing. Confirm the Delete checkbox only after checking the selected ID. On resource pages, also check the subscription and resource group. They can differ between pages.
Step 3: protect values that are not inventory
Inventory omits client secrets, account keys, Function keys and private app settings. A newly generated client secret is shown once in the Credentials tab; copy it into private configuration and clear the widget. App setting values use a masked input and are cleared after submission. Screenshots do not reveal these values, and this book does not teach you to paste them into resource names, tags or diagnostic logs.
Step 4: read asynchronous state
Create acknowledges a request. Deployment operations and external runtimes can still be Updating. Refresh and inspect the resulting state. A site with no image is intentionally Stopped; an app awaiting a helper is not ready. A stale helper heartbeat stops gateway forwarding even if the container still exists. For recovery, inspect the operator logs before submitting another Create.
QHQ launch settings
| Option | Value and effect |
|---|---|
--endpoint |
HTTPS origin; default https://localhost:11443 |
--credentials |
Bootstrap credential file; default /var/lib/quinzee/credentials.json |
--ca-file |
Trust certificate for the endpoint; default /etc/quinzee/tls/ca.crt |
--backend |
rasta, framebuffer or offscreen; default rasta |
--width, --height |
320–7680 pixels; defaults 1600 × 1000 |
--scale |
0–4; 0 selects automatic scaling |
--framebuffer |
Device path or Rasta framebuffer file |
--host, --port |
Rasta viewer address and UDP port; use the viewer's matching settings |
--assets |
Asset directory; defaults beside the executable |
--screenshot |
Output PNG; selects offscreen rendering and exits after loading |
--page, --tab |
Navigation ID and zero-based tab for screenshots; defaults overview/0 |
--help |
Show supported arguments |
The Rasta viewer settings are local display transport, not cloud HTTP ports.
Do not confuse its --port with the cloud's --port. The safe capture procedure
in the final chapter uses only disposable credentials and known public views.