Concepts
The mental models — GitOps, operators, the single edge, canary delivery, secrets. Start here if it’s been a while. New term? Check the Glossary.
Project Loom
Project Loom. One playbook weaves any app onto any of our servers.
Project Loom is a GitOps + progressive-delivery platform on k3s and Argo. It is app-agnostic: apps onboard through one repeatable playbook. Penvoice and Talon are examples — Ayde, Z1, or the next hundred follow the same Git layout on this or another server.
New node: Provision from scratch. New app: Onboard.
This guide is the map: provision a node, onboard the next app, operate deploys, restore after a cluster already existed.
How to read this
Section titled “How to read this”Onboard an app
The reusable recipe with copy-paste templates (placeholders you fill in): containerize → CI → database → deploy → canary. Follow this for the next app.
Worked examples
The same recipe, filled in for real apps — Penvoice’s API, Keycloak, the web app’s two environments, and backups.
Provision / restore
From scratch is a new node. Restore is after you already had a cluster.
At a glance
Section titled “At a glance” Architecture The platform design — topology, layers, how apps plug in.
Reference This instance's facts — endpoints, versions, namespaces, secrets.
Glossary Every acronym and bit of jargon, defined plainly.