chant on Fly and containers
llms.txt lists every page for an agent
For a team that runs on Fly Machines and containers: Apps and Machines applied straight to the Machines API, Sprites for sandboxes, and Docker files from the same TypeScript.
Works
- Fly Apps and Machines applied straight to the Machines API by
flyApply, with no flyctl and no state file - The whole deploy offline against the mudflaps emulator first, then against real Fly by dropping one override
- Sprites as disposable build sandboxes and agent workers, rewound to a checkpoint when a step fails
- Docker Compose services and multi-stage Dockerfiles from TypeScript
Differs
By forge
--generate githubwrites the pull-request workflow under.github/workflows/, run onpull_requestand onpushto the target branch.- Both jobs use the job's own
github.token. On a pull request from a fork that token is read-only, so the plan note and the status are not posted.
--generate gitlabwrites.gitlab-ci.yml, andapplyruns one at a time per environment throughresource_group.- A CI job token cannot write merge request notes, so set a project access token with the
apiscope as the masked variableCHANT_FORGE_TOKEN.
--generate forgejowrites the GitHub workflow in the Forgejo dialect under.forgejo/workflows/: the runner label, action references by URL, and nopermissionsblock.- Forgejo workflows are GitHub-dialect, so
chant auditapplies its GitHub rules to them.
First step
npm install --save-dev @intentius/chant-lexicon-flynpx chant init my-app --lexicon flyShow the whole prompt
Read https://intentius.io/chant/for/fly/.
Set up chant with the fly lexicon in this repository.
Install it with `npm install --save-dev @intentius/chant-lexicon-fly`, run `npx chant init . --lexicon fly`, and read every `skills/*/SKILL.md` it writes before you author anything.
Run `npx chant build` and `npx chant lint` until both pass, and open a pull request with the result. Deploy only to the mudflaps emulator, and only when I ask.
Never deploy to a real cloud account or shared environment (with `chant run`, `chant components` or a platform's own CLI), approve (a pull request review, `chant approve` or `chant run approve`), override a policy denial (`chant approve policy-override`), or merge; never cut or publish a release (`chant release cut --yes` or `chant release publish`), push or delete a `ci/*` tag (`chant ci tick` pushes them), or change the value of an existing flag; never touch `.chant/allowed_signers` or `chant/lifecycle`.Proof
Example projects in the chant repository for this room, each with a README that has the commands to run it. The last rows count the examples each lexicon ships, read from the repository when this site was built.
| Example | Where |
|---|---|
local-fly | examples/local-fly |
fly-reconcile | examples/fly-reconcile |
fly-deploy-rollback | examples/fly-deploy-rollback |
sprites-build-sandbox | examples/sprites-build-sandbox |
| 2 examples | lexicons/fly/examples |
| 3 examples | lexicons/docker/examples |
| 1 example | lexicons/render/examples |