Forking & Repointing¶

You can fork this stack, personalize it, and repoint it at your own managed set of repositories (Pi core, config preset, and extensions) instead of the LocalPibox originals.

What each component maps to¶

Component	URL / ref lives in	Effort	Repoint path
Extensions (lemonade-pi-plugin, lpb-memory, pi-subagents, …)	runtime config `~/.pi/agent/settings.json` → `packages`	🟢 trivial, no rebuild	edit the `packages` array, or `pi install git:<fork>/<repo>@<ref>`; applied at next startup
Config preset (lpb-stack/config)	`lpb.stack.env` → `LPB_CONFIG_FORK` / `LPB_CONFIG_REF`	🟡 one rebuild, or live at runtime	rebuild with `--build-arg CONFIG_FORK=...`, or repoint the clone in the running container (below)
Pi core (lpb-stack/pi)	`lpb.stack.env` → `LPB_PI_FORK` / `LPB_PI_REF`	🔴 image rebuild	fork `lpb-stack/pi`, set `LPB_PI_FORK`/`LPB_PI_REF` + image names, rebuild

Full repoint procedure (image build)¶

Fork the repos you care about (e.g. lpb-stack/pi, lpb-stack/config).
Clone this repo (devstack) and edit lpb.stack.env at the root to point at your forks:

export LPB_PI_FORK=https://github.com/<you>/pi.git
export LPB_PI_REF=main                 # your branch
export LPB_CONFIG_FORK=https://github.com/<you>/config.git
export LPB_CONFIG_REF=main             # your branch
export LPB_IMAGE_CLI=ghcr.io/<you>/devstack:dev-cli
export LPB_IMAGE_WEB=ghcr.io/<you>/devstack:dev-web
export LPB_CONTAINER_NAME=mybox        # avoid colliding with lpb-stack

(Or pass them as docker build --build-arg PI_FORK=... --build-arg CONFIG_FORK=... without editing the file.) 3. Build and push the image (locally, or via a fork of the GitHub Actions workflow, which reads lpb.stack.env). 4. Install and run lpb — it reads the same lpb.stack.env for image/container names, so it picks up your fork automatically. 5. To pin a specific image version persistently, export LPB_IMAGE_TAG=0.0.1-lpb-dev (a version tag on your fork's registry) — or let lpb resolve the latest for your pipeline.

Repointing the config preset without a rebuild¶

The config preset is a git clone at ~/.pi/agent/ (container). After first boot you can repoint it live — no image rebuild needed:

podman exec -it lpb-stack bash
cd ~/.pi/agent/
git remote set-url origin https://github.com/<you>/config.git
git pull --ff-only origin <your-branch>

start.sh only does a non-destructive git fetch on later boots (it never wipes local changes — use lpb-config update/reset/merge for actual updates). The clone is the live config directory, so pulled files are in place at the next Pi start.

Repointing extensions at runtime (no rebuild)¶

Extensions are not baked into the image; they are installed from settings.json#packages. Repoint them from the running container:

podman exec -it lpb-stack pi remove git:github.com/lpb-stack/lemonade-pi-plugin
podman exec -it lpb-stack pi install git:github.com/<you>/lemonade-pi-plugin@<your-ref>
podman exec -it lpb-stack pi update --extensions

Changes apply at the next pi startup (or /reload in a running session for config-only changes).