joakimp/mempalace-toolkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Compare commits

base: joakimp/mempalace-toolkit:46bcce5a6731b1bc6b445247b8d19395a1480ad2
Branches Tags
joakimp/mempalace-toolkit:main
...
compare: joakimp/mempalace-toolkit:98baabe7a0017f6893352b08de6953e51cf33e09
Branches Tags
joakimp/mempalace-toolkit:main

2 Commits
46bcce5a67 ... 98baabe7a0

Author SHA1 Message Date
Joakim Persson 98baabe7a0 contrib: flag cron-not-installed as a common caveat 
Minimal Debian/Ubuntu hosts (and most base container images) don't
ship cron by default. `crontab: command not found` is the first
thing a user hits if they try the cron path without installing it.
Previous caveats block covered semantics (no Persistent, mail-drop
stderr) but silently assumed cron was present. Add an explicit
"check command -v crontab, apt install cron, or pick systemd"
preflight to the caveats so the error is surfaced before the
user runs into it.

Caught during 2026-04-30 Phase 4 runtime validation on a Debian
trixie host: `crontab -T` lint failed because cron wasn't
installed, even though the underlying docker-exec shell command
(the actual workload) ran fine.
 2026-04-30 21:00:53 +00:00
Joakim Persson 00ce8a7fa1 contrib: clarify when opencode-devbox bakes in the toolkit 
Previous wording claimed opencode-devbox "bakes it in via
mempalace-toolkit" as if that were always true, but until
opencode-devbox v1.14.30b the image only shipped the mempalace
Python package, not the toolkit wrappers. Users following the
*-devbox scheduler docs on earlier images would hit
"mempalace-session: command not found" inside the container.

Rewrite the precondition to:
  - Name the version where bake-in starts (v1.14.30b).
  - Link to the upstream INSTALL_MEMPALACE_TOOLKIT build arg.
  - Document the escape hatch for custom/older containers
    (./install.sh --yes) and flag its ephemeral nature, so nobody
    leans on the manual install as a long-term solution.

Caught during 2026-04-30 runtime validation of the *-devbox
systemd unit on a freshly-rebuilt container.
 2026-04-30 20:57:13 +00:00
1 changed files with 2 additions and 2 deletions
Expand all files Collapse all files
contrib/README.md
+2 -2
View File
@@ -140,7 +140,7 @@ rm ~/Library/LaunchAgents/se.jordbo.mempalace-session.plist
**Why:** simpler, ubiquitous, works on any UNIX. No `loginctl enable-linger` dance, no user-units awareness required. **Why:** simpler, ubiquitous, works on any UNIX. No `loginctl enable-linger` dance, no user-units awareness required.
**Caveats:** no "persistent" semantics (a missed run while the machine was off stays missed); default cron output goes to mail or is silently dropped if no MTA. **Caveats:** no "persistent" semantics (a missed run while the machine was off stays missed); default cron output goes to mail or is silently dropped if no MTA. Also: **cron is not installed by default on minimal Debian/Ubuntu hosts** (nor on most container images). Check with `command -v crontab` — if absent, `sudo apt install cron` (or equivalent) first, or use the systemd timer instead.
**Install:** **Install:**
@@ -203,7 +203,7 @@ If you run opencode inside a long-lived container like [opencode-devbox](https:/
Preconditions: Preconditions:
- **Long-lived container.** `docker compose up -d` with `restart: unless-stopped` (or equivalent). If the container is ephemeral (per-invocation), this pattern doesn't apply. - **Long-lived container.** `docker compose up -d` with `restart: unless-stopped` (or equivalent). If the container is ephemeral (per-invocation), this pattern doesn't apply.
- **`mempalace-session` is already installed inside the container.** opencode-devbox bakes it in via `mempalace-toolkit`, so a running devbox already satisfies this. - **`mempalace-session` is already installed inside the container.** opencode-devbox bakes it in from `v1.14.30b` onward (see the [`INSTALL_MEMPALACE_TOOLKIT`](https://gitea.jordbo.se/joakimp/opencode-devbox#build-args) arg). For earlier images or custom containers without the toolkit installed, run `./install.sh --yes` from a `mempalace-toolkit` checkout inside the container first — the installer is idempotent and safe to re-run. Note that a manual install lives in the container's ephemeral layer and is lost on `docker compose up --force-recreate`, so the bake-in approach is the durable solution.
- **Host user can talk to docker.** Member of the `docker` group on Linux, or Docker Desktop running under the current login session on macOS. - **Host user can talk to docker.** Member of the `docker` group on Linux, or Docker Desktop running under the current login session on macOS.
- **Canonical container name is `opencode-devbox`.** If you renamed it via `container_name:` or docker-compose project naming, adjust `CONTAINER` in the template. - **Canonical container name is `opencode-devbox`.** If you renamed it via `container_name:` or docker-compose project naming, adjust `CONTAINER` in the template.