Evaluating chant

For someone deciding whether chant fits: what it is, how it compares, and a project that runs on your own machine with no cloud account.

Works

• A getting-started example that teaches chant in levels, starting with build, lint and list on nothing but Node
• Local emulators for AWS, Azure, GCP and Fly, so a deploy runs with no account
• Plain CloudFormation, Kubernetes YAML and workflow files, which keep working if you stop using chant

Differs

By forge

GitHub

• --generate github writes the pull-request workflow under .github/workflows/, run on pull_request and on push to 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.

GitLab

• --generate gitlab writes .gitlab-ci.yml, and apply runs one at a time per environment through resource_group.
• A CI job token cannot write merge request notes, so set a project access token with the api scope as the masked variable CHANT_FORGE_TOKEN.

Forgejo

• --generate forgejo writes the GitHub workflow in the Forgejo dialect under .forgejo/workflows/: the runner label, action references by URL, and no permissions block.
• Forgejo workflows are GitHub-dialect, so chant audit applies its GitHub rules to them.

First step

git clone https://github.com/INTENTIUS/chant
cd chant/examples/getting-started
npm install
npm run build

Quick Start

Or hand this step to your coding agentIt stops at a pull request or a report.

Read https://intentius.io/chant/for/evaluate/.
In a new directory, clone https://github.com/INTENTIUS/chant, and in `examples/getting-started` run `npm install` and `npm run build`.
Show me the output, and tell me what the example built and where it wrote it. Change nothing outside the new directory.
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`.

Show the whole prompt

Read https://intentius.io/chant/for/evaluate/.
In a new directory, clone https://github.com/INTENTIUS/chant, and in `examples/getting-started` run `npm install` and `npm run build`.
Show me the output, and tell me what the example built and where it wrote it. Change nothing outside the new directory.
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`.

Copy promptCopy link

Proof

Example projects in the chant repository for this room, each with a README that has the commands to run it.

Example	Where
getting-started	examples/getting-started
local-cloud-trio	examples/local-cloud-trio
local-op-quickstart	examples/local-op-quickstart

Then read

Tasks

Quick StartLocal Testing

Background

IntroductionWhat chant isHow chant comparesPhilosophy

Reference

Project StructureCLI overview