CLANKER.NET docs

CLANKER.NET gives every engineer on your team a ready-made development environment — a pod — on a host in your own cloud accounts, built from the repositories you already have. Nothing of yours passes through us: the factory runs from your repository, with your credentials, and we hold none of them.

How it fits together

Three files, two owners, one host:

flowchart LR
  subgraph team["Your team's repositories"]
    dc["<b>Dev-container file</b><br/>one per repository<br/><i>what a container of this repo is</i>"]
  end
  subgraph owner["The host owner's repository"]
    fleet["<b>Fleet file</b><br/>one per host<br/><i>which repos, at which ref, who may hold them</i>"]
    host["<b>Host spec</b><br/><i>where it runs — by name, never a secret value</i>"]
    caller["<b>Workflow</b><br/>one job that calls ours"]
  end
  subgraph cloud["Your cloud accounts"]
    machine["<b>Host</b><br/>reverse proxy · private network · tunnel"]
    podA["Pod: alice"]
    podB["Pod: bob"]
  end
  dc --> fleet
  fleet --> caller
  host --> caller
  caller -- "provision / sync / select" --> machine
  machine --- podA
  machine --- podB
  • A dev-container file (.devcontainer/devcontainer.json) sits in each repository, owned by the team that builds in it. It is the standard file any editor understands; the few things the standard cannot say go under customizations.clankernet. → The dev-container file
  • A fleet file (factory.yml) sits in the host owner’s repository and says which repositories every pod on that host holds, at which ref, and who may hold them. → The fleet file
  • A host spec (hosts/<name>.yml) says where — which accounts, which network, where state and secrets live — naming every credential, never holding one. → Host specs

The host owner runs the host up once. Each engineer provisions once and gets a pod: one container per repository with a dev-container file, a shared clone of each one without, one public name, one address on your private network, and an ssh port per repository. Switching which repository the public name shows takes seconds and restarts nothing.

Start here

PageForWhat it answers
QuickstarteveryoneFrom nothing to a pod on your own host: the files, the workflow, the secrets
The dev-container fileadoptersThe per-repo file: standard fields, the clankernet block, what is refused
The fleet filehost ownersThe per-host file: the repositories, the pod, the switch, keeping it converged
Host specshost ownersWhere it runs: compute, ingress, DNS, access, secrets and state — by name
Bring your own cloudhost ownersWhat you need, what we hold (nothing), what is in your state, the limits
DNS ownershiphost ownersWhich records the factory writes, how they are tagged, what it never touches

The pages describe what the factory does for you, not what it is built from; a literal key or value appears where a reference needs it.