repositories / pi-ext

pi-ext

bugabingas pi extensions

owned by bugabinga

docs: simplify README — separate user and dev install sections

6b351accda4c6ccfaa6e95732fc2a67424a77928

Oliver Jan Krylow <oliver@bugabinga.net> ·

unsigned

Browse filesCompare with HEAD

Changed files (1)

README.md

Modified
9 9 Never `pi ext install`.
10 10 That corpse stays buried.
12 -All extensions via git, pinned:
12 +Pinned version:
14 14 ```bash
15 15 pi install git:github.com/bugabinga/pi-ext@v0.0.3
18 -Default branch install:
18 +Default branch:
20 20 ```bash
21 21 pi install git:github.com/bugabinga/pi-ext
24 -Local checkout, absolute path:
24 +### Filtering
26 -```bash
27 -pi install /home/me/Workspace/pi-ext
28 -```
30 -Local checkout, `~` path:
32 -```bash
33 -pi install ~/Workspace/pi-ext
34 -```
36 -Single-extension package filter in `~/.pi/agent/settings.json`:
26 +Load only a subset via `~/.pi/agent/settings.json`:
38 28 ```json
130 120 Less accounting.
131 121 Fewer tiny coffins.
123 +## Development
125 +Clone locally, install dependencies, then point Pi at the path:
127 +```bash
128 +git clone https://github.com/bugabinga/pi-ext.git
129 +cd pi-ext
130 +bun install
131 +pi install /absolute/path/to/pi-ext
132 +```
134 +Or add to `~/.pi/agent/settings.json`:
136 +```json
138 + "packages": [
140 + "source": "/absolute/path/to/pi-ext"
144 +```
146 +> **Note:** Local paths and git sources both require manual dependency installation. Pi runs `npm install --omit=dev` for git sources, but ignores `bun.lock`. In practice npm 7+ resolves the workspace correctly. For local development, run `bun install` inside the repo first.
135 150 Fat prompts rot in bins.\