start-temps

# Start a local Temps server Boots the `temps` binary from source (`cargo run --bin temps --package temps-cli -- serve ...`) for quick local iteration, no debugger required. See `CONTRIBUTING.md` for the one-shot manual version of this; this skill adds port isolation across worktrees and a repeatable restart flow. ## Prerequisites - The database container from `CONTRIBUTING.md` ("Database" section) running and reachable, e.g.: ```bash docker run -d --name temps-db --restart unless-stopped \ -p 127.0.0.1:5432:5432 \ -v temps-db-data:/home/postgres/pgdata/data \ -e POSTGRES_USER=temps -e POSTGRES_PASSWORD=temps -e POSTGRES_DB=temps \ timescale/timescaledb-ha:pg18 ``` If your container has a different name, user, password, or port, set `TEMPS_DEV_DB_CONTAINER` / `TEMPS_DEV_DB_URL_BASE` before running step 0, or just edit the generated slot env file afterwards. - `bun install` already run in `<checkout>/web`. - Docker running, if you'll exercise features that shell out to it (container deploys, agent sandboxes, etc.) — see the Docker precheck below. ## Port slots — read this first If you keep multiple worktrees of this repo around (one per branch/PR), the naive approach — hardcode `:8080` / `:3000` and kill whatever's listening — means starting temps in worktree B kills the server another session was using in worktree A. This skill instead assigns each checkout a *slot* (0–29) and derives every port from it: | Thing | Port | Slot 0 | |---|-...