Stax Digital Garden

QTM-1001 - Fleet Operations on Modest Hardware

4 min read

Living Document Notice
Published 2026-09-10. The evolving architecture, revisions, and connected notes for this dispatch live in the Stax Digital Garden.

Fleet Operations on Modest Hardware

Fleet Operations on Modest Hardware: Emerald green P31 stepped balance waveform and baseline equilibrium line with warm golden-amber P20 diamond audit nodes and boundary bars

Summary

Modern deployment architectures frequently over-engineer web publishing by introducing distributed Kubernetes clusters, heavyweight container runtimes, and complex cloud observability pipelines for simple multi-tenant workloads. These stacks demand significant compute overhead and require dedicated operations personnel to maintain.

Quartermaster manages multi-tenant digital garden publishing across economical single-core VPS nodes and modest bare-metal hardware. By relying on plain configuration manifests, declarative shell provisioning, and lightweight reverse proxies, Quartermaster delivers stable multi-site hosting with minimal resource consumption.

Operational Efficiency on Constrained Nodes

Hosting fourteen distinct digital garden publications does not require large-scale cloud infrastructure. A single virtual private server provisioned with one gigabyte of RAM and twenty gigabytes of solid-state storage can serve millions of static HTTP requests when decoupled from heavy dynamic application runtimes.

Quartermaster enforces a strict resource budget across all nodes. Applications must run without memory leaks, long-lived compilation daemons, or unnecessary background background workers.

+-------------------------------------------------------------+
|             Quartermaster Single-Node Layout                |
|                  Hardware: 1 vCPU / 1 GB RAM                |
|                                                             |
|  +-------------------------------------------------------+  |
|  | Linux Kernel (Debian Minimal / Alpine Linux)          |  |
|  |                                                       |  |
|  |  +-------------------------------------------------+  |  |
|  |  | Nginx / Caddy Edge Proxy (HTTP/2, Let's Encrypt)|  |  |
|  |  +-------------------------------------------------+  |  |
|  |             |                       |                 |  |
|  |             v                       v                 |  |
|  |  +---------------------+  +---------------------+     |  |
|  |  | Directus Node (384MB)|  | Static Site Roots   |     |  |
|  |  | SQLite Backend Engine|  | (Pure HTML / Quartz)|     |  |
|  |  +---------------------+  +---------------------+     |  |
|  |             ^                       ^                 |  |
|  |             |                       |                 |  |
|  |  +-------------------------------------------------+  |  |
|  |  | Quartermaster Dispatch Runner (Cron / POSIX sh) |  |  |
|  |  +-------------------------------------------------+  |  |
|  +-------------------------------------------------------+  |
+-------------------------------------------------------------+

Static publication artifacts reside directly in root directories managed by the web server. Directus handles administrative content operations through an embedded SQLite database, bypassing the memory overhead of external database servers.

Declarative Provisioning Manifests

Fleet nodes are provisioned using flat YAML manifests that specify system users, packages, directory layouts, and proxy configurations. Quartermaster avoids dynamic orchestration agents by parsing these manifests with lightweight POSIX shell scripts.

ComponentTarget AllocatorMemory CeilingStorage Constraint
caddy-proxyEdge routing45 MBSystem log rotation cap: 50 MB
directus-coreHeadless CMS384 MBEmbedded SQLite with WAL mode
static-gardensHTML / CSS / JS0 MB (Kernel cache)Bound by static disk quota
crows-nestTelemetry probe12 MBFlat text log buffer

The node configuration manifest specifies deterministic environment baselines:

version: "1.0"
node:
  hostname: "vps-lon-01"
  provider: "bare-vps"
  ram_mb: 1024
services:
  caddy:
    enabled: true
    config_path: "/etc/caddy/Caddyfile"
  directus:
    enabled: true
    port: 8055
    db_client: "sqlite3"
    db_filename: "/data/directus/data.db"
    max_memory_mb: 384
sites:
  - domain: "garden.bosunpkm.com"
    root: "/var/www/garden"
  - domain: "freemydata.tech"
    root: "/var/www/freemydata"

Provisioning updates execute idempotently. System configuration diffs apply sequentially, terminating on non-zero exit codes to prevent broken deployment states.

Provisioning Invocations and Baseline Checks

System administrators verify node hardware baselines and provision updates using minimal CLI commands:

`ash

Verify system resource utilization against memory ceilings

free -m && df -h /data

Execute Quartermaster node reconciliation pipeline

quartermaster-cli apply —manifest /etc/quartermaster/node.yaml

 
## Low-Resource Failure Boundaries
 
Running multi-tenant workloads on constrained hardware exposes specific physical boundaries:
 
1. Kernel OOM Killer Invocations: When build tasks spike memory usage, the Linux kernel terminates high-memory processes unless memory cgroups configure strict resource ceilings.
2. Disk I/O Starvation: Inexpensive shared VPS hosting often throttles disk IOPS during sustained writes, requiring SQLite transactions to batch writes using memory-mapped temp stores.
3. SSL Certificate Renewal Collisions: Automatic Let's Encrypt challenges fail if ACME client rate limits trigger during simultaneous domain renewals across multi-tenant sites.
 
---
* **Directus Target**: quartermaster
* **Garden Source Reference**: MOC - Fleet Operations
* **Garden Source Reference**: MOC - Bosun PKM Tools
* **Garden Source Reference**: [QTM-1001 - Fleet Operations on Modest Hardware](QTM-1001 - Fleet Operations on Modest Hardware)

Graph View