Set Up the CLI
Four commands. The last one is the point — no .env on disk means no drift, no stale value, and nothing to commit by accident.
1
Install
Not published yet — the release pipeline is still being built. For now, build from the repo.
git clone git@gitlab.antikode.com:frontend-dev/anti-env.git cd anti-env/cli && go build -o ~/.local/bin/anti-env ./cmd/anti-env
2
Log in
Opens Lark in your browser and stores a 7-day token in ~/.config/anti-env/token.json.
anti-env login
3
Point the repo at a config
Writes .anti-env.json, which is committed. It names the project and environment — never a value.
cd ~/Projects/Antikode/…/your-repo anti-env setup
4
Run your dev server through it
Secrets are injected into the child process and never touch the filesystem.
anti-env run -- npm run dev # package.json "dev": "anti-env run -- next dev"
Everything else
- anti-env pull --out .env — when a tool genuinely needs a file on disk
- anti-env import .env — first-time upload of an existing file
- anti-env diff — local vs remote, or one environment vs another
- anti-env doctor — when something is wrong and you would rather not guess
Membership and grants are managed here in the dashboard, not from the CLI. That is deliberate: access changes should leave a trail someone can read.