There was an error while loading. Please reload this page.
Add the Fleet GitOps lab walkthrough A Fleet server, a Gitea server with CI, and a runner that applies config to Fleet on every push — all in Apple containers, no Docker. Written from actually building it rather than from the upstream docs, so the failures are in it: fleetctl refusing a plain-http address, Fleet excepting enroll secrets from GitOps by default, the runner base image lacking node and perl, and the one that matters most — Fleet running happily for an hour on the default memory and then going silent when its vulnerability cron fires, with no error anywhere to explain it. Each is written next to the step that prevents it. Also records the two decisions a reader would otherwise get wrong: the compose file's certificate mounts have to exist even with TLS off, and mysql's x86 pin should go while fleet's should stay. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add user documentation Eleven pages plus a sidebar: a quick start that gets to a running web app, worked examples, a guide per section, and troubleshooting organised by the symptom rather than the subsystem. Written around the one constraint that explains most of the app's design — containers reach each other by address, not name — since coming from docker-compose without knowing that makes several behaviours look arbitrary. It's stated on the home page, explained under Stacks, and its limits are spelled out under Local DNS, which people will otherwise expect to fix it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>