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.

Administrator’s guide

1. Start with a small, understood installation

An administrator's first responsibility is to know which process owns which state. Quinzee Cloud serves the local Azure-compatible APIs. QHQ is a client of those APIs, not the server. The DNS process answers names. Separate helpers run SQL/cache engines and hosted applications. A running QHQ window does not prove that all of those processes are healthy.

This book starts with one local development installation. It then explains how to operate each part separately. Quinzee is a single-tenant compatibility platform with bounded service implementations; it is not an Azure control plane, a Windows domain controller or a highly available production directory. Treat its credentials, application data and backups as private even in a local lab.

Step 1: prepare the operator workstation

Use the verified Linux x86-64 platform. Install the repository's supported C++ build toolchain, Docker/Compose, Python 3 and OpenSSL. The host or development image needs CMake, a C++20 compiler, Make, Git, curl, Perl, bzip2, Bison and Flex. The real hosted .NET examples additionally need .NET SDK 10. QHQ's graphical viewer needs a Linux graphical session; offscreen screenshots do not.

Run these from the repository root:

make deps
make
make test
make certs

Dependencies are verified and cached in .packages/; binaries go into bin/debug/. The first run can need downloads and time to compile. A later cached build should reuse them. A missing compiler or failed check is an installation problem to fix before provisioning application data.

Step 2: start a default local environment

make qhq-run

This is the convenient operator lab: it starts the HTTPS cloud and DNS containers and opens QHQ through the Rasta viewer. By default, the host connects to https://localhost:11443, and state is in .local/quinzee. Certificate material is in .local/certificates. Bootstrap credentials are generated at first startup in the private credentials.json inside the cloud data directory. There is no default human administrator password.

Wait for QHQ's Connected indicator. Open Emulator → Overview and verify the endpoint and tenant before changing anything. Then open Modules. All default modules should be loaded; LDAP's optional external listener can still be unconfigured. SQL or hosted apps need their helpers before their workloads run.

Overview in a disposable environment

The screenshot uses synthetic resources and a temporary port. Your persistent installation's values differ. Screenshots throughout this guide are real QHQ captures; the UI atlas includes every page and its actual tabs.

Step 3: prove HTTPS independently

In another host terminal:

curl --fail --silent --show-error \
  --cacert .local/certificates/ca/quinzee-dev-root-ca.crt \
  https://localhost:11443/health

Expect a healthy quinzee.cloud response. A refused connection means listener, process or port mapping trouble. A certificate error means trust, hostname or certificate trouble. Fix the actual layer; adding -k would hide the problem that your SDK clients will encounter.

Step 4: stop without deleting the installation

Close QHQ and run make qhq-env-down. Containers stop; the data directory remains. Starting again reuses the tenant and resources. For cloud-only use, make cloud-up and make cloud-down control the Compose services. Stopping a helper or unloading a module is not the same as stopping its workloads; later chapters give the correct order for each service.

Do not use make purge as routine shutdown: it is destructive. Resource-group Delete is also a data-removal operation, not a way to pause a project.

Step 5: distinguish the two standard labs

make application-up runs the browser demonstration in its own persistent folder, .local/application/development. It can choose different ports, a different Docker network and different credentials. make application-test uses an isolated disposable environment. Never point QHQ at one lab while reading credentials or certificates from the other. Record each installation's origin, data path, trust root and network as one set.