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.
15. Stop, restart and clean up safely
There are two useful environment entry points. Do not mix their state paths, credentials or Compose commands accidentally.
| Environment | Start | State | Stop |
|---|---|---|---|
| Application tutorial | make application-up or make application-observability-up |
.local/application/development plus owned engine volumes |
Exit attached development containers, then Ctrl+C in the helper terminal |
| Standalone cloud + DNS | make cloud-up |
.local/quinzee, certificates in .local/certificates |
make cloud-down |
| Functions helper for standalone cloud | make functions-run |
.local/functions-helper, plus cloud mailbox state |
Stop apps through ARM/QHQ and wait, then Ctrl+C in the helper terminal |
| Optional telemetry tools | make observability-up |
.local/observability |
make observability-down |
The application helper generates its own Compose project, subnet and cloud
port. Its browser port is normally 3000. The standalone cloud uses
https://localhost:11443, AMQP/TLS on loopback port 5671, DNS diagnostics on
loopback port 10053 and the
triglav-http_quinzee network by default. Native engine ports are accessible
inside their private network, not published on the host.
Step 1: stop without deleting data
- Finish or cancel your client work. Cancellation can leave already-created resources; it does not roll back a deployment.
- Exit the SDK container with
exit, so it no longer holds the private network open. - Close QHQ and stop its Rasta viewer if you started it separately.
- Press Ctrl+C in the application helper terminal. It stops the environment and preserves its state and engine volumes.
- Run
make observability-downif you also started the external tools.
Run the same application command later to reuse the environment. Existing accepted monitoring rows, blobs, queue leases, secrets, settings and native volumes survive this stop/start cycle. A deployment interrupted while running is marked failed on restart; redeploy it after checking what completed. Create fresh credential/client instances after a cloud restart if old cached bearer tokens are rejected.
For the standalone setup, make cloud-down stops the cloud/DNS services but
does not manage separately operated engine containers. Stop SQL resources
through QHQ/ARM or delete the resources deliberately. Simply stopping the
standalone supervisor leaves engines running. Likewise, stop function apps
through QHQ/ARM while the Functions helper is running and wait for Stopped
before ending that helper. Otherwise Service Bus triggers can keep consuming
messages even after HTTP forwarding has stopped. Service Bus queues, topic
copies and locks persist across a normal cloud restart.
Step 2: delete only the tutorial resources
This step destroys the book's resources and their data, including SQL/Redis volumes. Run it only when you have finished the service exercises. Keep the application helper and SDK container running until deletion completes. Replace Program.cs with:
using Azure;
using Azure.Core;
var book = BookContext.Load();
if (!book.Settings.Group.StartsWith("quinzee-book-", StringComparison.Ordinal))
throw new InvalidOperationException("This example only deletes its tutorial group");
Console.WriteLine($"Deleting tutorial group: {book.Settings.Group}");
var group = book.Arm.GetResourceGroupResource(new ResourceIdentifier(book.GroupId));
await group.DeleteAsync(WaitUntil.Completed);
Console.WriteLine("Tutorial resources deleted; unrelated groups were not selected.");
The browser application's Cleanup action targets its own application group, not this book's separate group. Deleting a completed deployment history entry also does not clean up its resources. Re-run chapters 4 and 5 to provision the book group again; the local project files and settings remain available.
The standalone messaging lab has a separate quinzee-messaging group. Follow
its cleanup procedure while the
Functions helper remains running to process runtime removal. Deleted function
app names stay reserved by tombstones, and private helper keys/parameter files
remain for explicit cleanup. Group deletion also destroys Service Bus messages.
Step 3: keep state and trust together
The application environment's private directory holds identity configuration, HTTP-service state, certificate material and helper logs. Native database data also lives in labelled Docker volumes; the engine supervisor's private CA/state is kept separately from the cloud's mount. Copying just the cloud directory is not a backup of the complete environment.
For a manual backup, stop client writes and all relevant processes, then save the cloud state, certificates, corresponding helper state and native volumes as one consistent set. Protect those copies as secrets. No automatic Azure-style backup/restore service is provided. Do not use broad Docker prune commands as a routine Quinzee shutdown procedure.
make clean removes build outputs, not runtime state. make purge additionally
removes dependency caches and the default Compose project's containers/images;
it is not needed for ordinary use or to refresh a browser page.
Logs and quick checks
For the application environment, inspect
.local/application/development/environment.log. For the standalone cloud,
use make cloud-logs. For telemetry tools, use make observability-status and
make observability-logs.
Cloud request logs are structured JSON. Trace IDs help connect related events; HTTP health does not prove that a particular database or queue worker is ready. Use QHQ's observability page or the authenticated diagnostics endpoint for that additional state.