quinzee.cloud

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.

Developer’s guide

14. Manage the environment with QHQ

QHQ—Quinzee Headquarters—is the native management application. It uses the same public HTTPS APIs as your C# clients. A graphical Linux session and SDL2 are needed for its Rasta development window.

Step 1: connect to the book's application environment

The tutorial environment has its own cloud port, data directory and CA. make qhq-run normally starts a separate default cloud environment, so use the following commands to connect to the one already running for the book.

On the host, from the repository root:

make qhq qhq-rasta-start
book_env="$PWD/.local/application/development"
book_port=$(python3 -c 'import json,sys; print(json.load(open(sys.argv[1]))["cloudPort"])' "$book_env/environment.json")
QUINZEE_HTTPS_PORT="$book_port" \
QUINZEE_DATA_DIR="$book_env/data" \
QUINZEE_CERT_DIR="$book_env/certificates" \
  bash scripts/dev/qhq.sh run

When you close QHQ, stop its viewer with bash scripts/dev/qhq.sh rasta-stop. The application environment stays running in its original terminal. If you started QHQ against the wrong instance, use Emulator → Connection to set the endpoint, credentials file and CA above, then connect. The credentials file is data/credentials.json, not the browser access-token file or the tutorial's filtered settings file.

For a separate standalone management environment, make qhq-run remains the convenient command; finish that session with make qhq-env-down.

QHQ displaying the browser demo's resource group

Choose a subscription, then inspect its resource groups. The endpoint port and resource names come from this disposable example environment; use your own. This 15 November capture predates the new Service Bus and Functions pages.

Step 2: navigate the service pages

Categories start collapsed. Expand a category, then choose its page. Pages may have tabs. Tab/Shift+Tab move between controls; Enter activates buttons. Use Refresh after an external SDK changes resources, and check the selected subscription/group before making changes.

Page Use it to
Emulator → Overview Check connection, endpoints, uptime and loaded services
Emulator → Connection Select the cloud URL, credential file and trusted CA
Emulator → Modules Inspect module state/dependencies and load or unload services
Emulator → DNS Inspect service/custom records and enable or disable Azure-name emulation
Azure / Entra ID → Tenant Inspect local tenant/authority details and obtain an access token
Azure / Entra ID → App registrations / Enterprise applications Create and edit registrations, credentials and service principals
Azure / Entra ID → Users / Groups Manage shared accounts, passwords and memberships
Azure / Entra ID → App roles / App role assignments Define API roles and grant them to users, groups and applications
Azure / Resource access → Managed identities / RBAC Create identities and assign scoped resource permissions
Windows / Directory → LDAP Inspect the shared backend/listener and open shared user/group management
Azure / App Service → Web apps / App Service plans Provision Linux hosting, attach identities, manage settings and lifecycle
Resource Manager → Subscriptions Inspect or manage local subscriptions
Resource Manager → Resource groups Create/list/delete groups with location and tags
Resource Manager → Deployments Submit compiled ARM JSON, inspect history and resource operations
Storage → Storage accounts Manage accounts and inspect endpoints
Storage → Queues Manage queues, send messages and peek without consuming work
Storage → Tables Inspect tables and work with typed entities
Event Grid → Topics Inspect topics and event subscriptions
Service Bus → Namespaces Inspect namespaces, queues, topics and subscriptions
Functions → Function apps Create/edit apps, attach identities, manage settings and Start/Stop/Restart
Key Vault → Vaults Manage vaults and secret values/metadata through the Secrets tab
App Configuration → Configuration stores Manage stores and labelled key-values
Databases and cache → PostgreSQL/MySQL Manage servers/database children and start/stop/restart SQL servers
Databases and cache → Managed Redis Manage the local encrypted cache and its database
Monitoring → Observability Inspect health, recent requests and workspace query results

Workspace and Application Insights component provisioning is through ARM/Bicep; there is no separate component-creation wizard in QHQ. Use the monitoring page to query their data after deployment. Service Bus provisioning uses the deployment page. Functions and App Service also have creation/editing forms. Their public inventory omits secret values; the App settings tab changes one private setting at a time. See the identity management walkthrough and web-app hosting guide.

Step 3: inspect your deployment

Choose the tutorial's quinzee-book-bk… group on the deployment page. Refresh, select book, and inspect its operations. To submit a new deployment in QHQ, provide a compiled JSON template and, where needed, an ARM parameters JSON file. A .bicep file is source code: compile it first. Keep secure parameter files private and do not paste passwords into tags or resource names.

A server can exist while its operation is still running. Refresh until the operation succeeds before using its native protocol. The engine helper must be running; QHQ does not have Docker-administrator powers of its own.

Step 4: use modules deliberately

An unloaded module retains its state, but requests for its service return 503. Reload it to resume. Module dependencies prevent removing a provider that is still required by another loaded module; identity cannot be unloaded. Unloading SQL modules is not the same as stopping their native database containers. Unloading Functions also leaves its external hosts and queue triggers running. Use Stop while the runtime helper is available and wait for the state change.

A resource Delete action is different: it removes the resource and may remove stored data. Use SQL Stop for a temporary pause, and reserve resource-group Delete for deliberate cleanup.