@cat-factory/cli 0.10.1 → 0.10.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +14 -9
- package/package.json +4 -4
package/README.md
CHANGED
|
@@ -3,8 +3,8 @@
|
|
|
3
3
|
The bootstrap CLI for [cat-factory](https://github.com/kibertoad/cat-factory), the Agent
|
|
4
4
|
Architecture Board. One command scaffolds a **local-mode deployment** you can run on your own
|
|
5
5
|
machine: a Node/local backend (`@cat-factory/local-server`) and the frontend SPA
|
|
6
|
-
(`@cat-factory/app`), mirroring the [`deploy/local`](
|
|
7
|
-
[`deploy/frontend`](
|
|
6
|
+
(`@cat-factory/app`), mirroring the [`deploy/local`](https://github.com/kibertoad/cat-factory/tree/main/deploy/local) and
|
|
7
|
+
[`deploy/frontend`](https://github.com/kibertoad/cat-factory/tree/main/deploy/frontend) example deployments in this repo, but depending on
|
|
8
8
|
the **published** libraries, so the generated project stands alone outside the monorepo.
|
|
9
9
|
|
|
10
10
|
It does the fiddly setup for you:
|
|
@@ -38,7 +38,7 @@ It does the fiddly setup for you:
|
|
|
38
38
|
described above.
|
|
39
39
|
- **`cat-factory env`**: generates **only** a ready-to-run local-mode `.env` in the current
|
|
40
40
|
directory (or `--dir`), using the same secret generation, PAT flow, and pool-vs-native choice.
|
|
41
|
-
Use it when the deployment already exists (e.g. inside [`deploy/local`](
|
|
41
|
+
Use it when the deployment already exists (e.g. inside [`deploy/local`](https://github.com/kibertoad/cat-factory/tree/main/deploy/local),
|
|
42
42
|
or an already-scaffolded project) and you just need a fresh, complete `.env`. It refuses to
|
|
43
43
|
overwrite an existing `.env` unless you pass `--force`, and (like `init`) it creates or merges
|
|
44
44
|
the target dir's `.gitignore` so the secret `.env` can never be committed. A model-provider key
|
|
@@ -194,15 +194,20 @@ cd local && npm install && npm run db:up && npm start # serves :8787
|
|
|
194
194
|
cd ../frontend && npm install && npm run dev # Nuxt dev on :3000
|
|
195
195
|
```
|
|
196
196
|
|
|
197
|
-
|
|
197
|
+
Expect the first `npm start` to sit there a while: before it serves anything, the backend pulls
|
|
198
|
+
the executor-harness image your agent jobs will run in, matched to the version it was built
|
|
199
|
+
against. Later starts reuse it. The generated `.env` leaves `LOCAL_HARNESS_IMAGE` commented out
|
|
200
|
+
so you stay on that matched pin; set it (or pass `--harness-image` at scaffold time) only when
|
|
201
|
+
you want to lock a specific version or run your own build.
|
|
198
202
|
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
+
The last thing to add is a **model provider**, without which the board comes up but no model is
|
|
204
|
+
selectable, so no pipeline can start. The quickest is Cloudflare Workers AI over REST
|
|
205
|
+
(`CLOUDFLARE_ACCOUNT_ID` + `CLOUDFLARE_API_TOKEN`); any direct vendor key works too, such as
|
|
206
|
+
`ANTHROPIC_API_KEY`. Put it in `local/.env` before you start, or sign in and add it through the
|
|
207
|
+
UI, whichever you prefer.
|
|
203
208
|
|
|
204
209
|
The generated `README.md` repeats these steps with your chosen values, and links to the full
|
|
205
|
-
[local-mode docs](
|
|
210
|
+
[local-mode docs](https://github.com/kibertoad/cat-factory/blob/main/deploy/local/README.md) (container-runtime matrix, repo linking, the
|
|
206
211
|
Tester's Docker-in-Docker / ephemeral environments, the warm container pool, etc.).
|
|
207
212
|
|
|
208
213
|
## Security notes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cat-factory/cli",
|
|
3
|
-
"version": "0.10.
|
|
3
|
+
"version": "0.10.2",
|
|
4
4
|
"description": "Bootstrap CLI for the Agent Architecture Board: scaffold a local-mode deployment (Node/local backend + frontend SPA) on your own machine — generates the crypto secrets, populates and gitignores the .env files, and mints a GitHub/GitLab personal access token by opening the browser at the right pre-scoped URL.",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"bootstrap",
|
|
@@ -37,12 +37,12 @@
|
|
|
37
37
|
"@clack/prompts": "^1.7.0"
|
|
38
38
|
},
|
|
39
39
|
"devDependencies": {
|
|
40
|
-
"@types/node": "^26.
|
|
40
|
+
"@types/node": "^26.2.0",
|
|
41
41
|
"typescript": "7.0.2",
|
|
42
42
|
"valibot": "^1.4.2",
|
|
43
43
|
"vitest": "^4.1.10",
|
|
44
|
-
"@cat-factory/contracts": "0.
|
|
45
|
-
"@cat-factory/kernel": "0.
|
|
44
|
+
"@cat-factory/contracts": "0.283.1",
|
|
45
|
+
"@cat-factory/kernel": "0.279.2"
|
|
46
46
|
},
|
|
47
47
|
"scripts": {
|
|
48
48
|
"build": "tsc -b tsconfig.build.json",
|