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

20. Run the emulator natively

The cloud and QHQ can be built and run as native Linux binaries. Docker is the integrated development setup used by the book; there is no packaged native installer or ready-made service-management setup in this repository.

After a native debug build, on the host:

make certs
bin/debug/quinzee.cloud \
  --address 127.0.0.1 --port 11444 \
  --data-dir "$PWD/.local/quinzee-native" \
  --tls-cert "$PWD/.local/certificates/quinzee.cloud/server.crt" \
  --tls-key "$PWD/.local/certificates/quinzee.cloud/server.key"

In another terminal:

curl --fail --cacert .local/certificates/ca/quinzee-dev-root-ca.crt \
  https://localhost:11444/health

This starts the HTTPS API and creates private identity/state for that directory. Add --service-bus-port 5671 to enable AMQP/TLS with the same TLS files; without it the Service Bus HTTPS API can be available while AMQP remains disabled. It does not automatically configure a DNS server, Azure listener, native engine supervisor or your application's trust store. --help lists configuration options, including module selection and the separate Azure-emulation listener.

Native SQL/Redis provisioning still uses the separate Docker-based supervisor. It needs a private state directory, the matching cloud mailbox directory and a Docker network reachable by the clients. Merely running the cloud binary natively does not replace the engine runtime with embedded databases.

Functions also needs its separate Docker helper, registered images and a reachable private bridge. A loopback-only cloud cannot serve the broker to function containers; configure the reachable address, DNS and trust explicitly. The helper takes the same cloud data directory, a separate private state directory, an approved image registry and an existing reachable Docker network. Run it as a non-root Docker operator; keep its private state outside cloud data. The hosting chapter gives the complete invocation.

For unattended use, arrange process ownership, startup ordering, logs, certificate renewal and consistent data backups explicitly. Bind only the interfaces you intend clients to reach. Never run two hosts against one writable data directory.

QHQ's Rasta backend provides a graphical development window. Its framebuffer backend can run on a Linux console with the required display/input access; those device permissions and an installation service are operator setup, not provided automatically by this tutorial.