@garaje/base 0.1.4 → 0.1.5

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@garaje/base",
3
- "version": "0.1.4",
3
+ "version": "0.1.5",
4
4
  "license": "MIT",
5
5
  "repository": {
6
6
  "type": "git",
@@ -13,6 +13,15 @@
13
13
  endpoint) to prove the change took effect.
14
14
  - `compose.framework.yaml` and `docker-compose.yml` are the framework
15
15
  substrate and are write-protected — propose changes, don't edit them.
16
+ - Pi extensions are **codified in the repo**, not installed ad hoc. Run
17
+ `pi install -l npm:<pkg>@<version>` — the `-l` writes the committed
18
+ `.pi/settings.json`, and teammates get the package automatically on their next
19
+ `garaje up`. Without `-l` the install lands in user scope on the pi-config
20
+ volume, where nobody else can see it. Always pin the version, then commit
21
+ `.pi/settings.json`. (`.pi/npm/` holds the artifacts and is gitignored.)
22
+ - Inference credentials live in `.env`, which compose forwards into this
23
+ container; that is the only surface. A key stored by `/login` is written to
24
+ `/root/.pi/agent/auth.json` on the pi-config volume and OVERRIDES `.env`.
16
25
  - `packages/` holds the garaje **framework** being extracted from this repo:
17
26
  `packages/cli` (the TypeScript `garaje` CLI) and `packages/base` (the
18
27
  `@garaje/base` pi package), as npm workspaces. The recipe→compose codegen now