Joakim Persson
7649d53f3b
Both keys shipped empty with no explanation, so they read as optional. They are not: ~/.gitconfig is not on a persistent mount, so with these unset every repo in the container fails "Author identity unknown" on first commit after every recreate — and an agent asked to commit then infers an identity from git log and picks the wrong one. Observed today across three repos on one machine (two wrong-address commits, plus older `pi <pi@devbox>` fossils from earlier sessions guessing the same way). Also records that the address is per-machine (corporate vs private), so it belongs in the per-machine .env rather than a skill or a repo-local override.
88 lines
4.8 KiB
Bash
88 lines
4.8 KiB
Bash
# pi-devbox environment configuration
|
|
# Copy this file to .env and fill in your values:
|
|
# cp .env.example .env
|
|
|
|
# ── Workspace ────────────────────────────────────────────────────────
|
|
# Path on host to mount as /workspace in the container
|
|
WORKSPACE_PATH=~/projects
|
|
|
|
# Path to SSH keys on host
|
|
SSH_KEY_PATH=~/.ssh
|
|
|
|
# ── MemPalace memory (local by default) ───────────────────────────
|
|
# By default the mempalace.ts extension spawns a LOCAL mempalace-mcp stdio
|
|
# server (palace at ~/.mempalace). Uncomment the devbox-palace volume in
|
|
# docker-compose.yml to persist it across container recreation.
|
|
#
|
|
# To instead share ONE MemPalace across containers/harnesses (pi + opencode
|
|
# + native), set the URL below. When set, the extension connects over HTTP
|
|
# and NO local mempalace-mcp is spawned; the devbox-palace volume is then
|
|
# irrelevant. MEMPALACE_REMOTE_TOKEN, if set, is sent as a bearer token.
|
|
# Serve it with: mempalace-mcp --transport http --host 0.0.0.0 --port 8765
|
|
# MEMPALACE_REMOTE_URL=http://mempalace.lan:8765/mcp
|
|
# MEMPALACE_REMOTE_TOKEN=
|
|
|
|
# ── LAN access from the container (host-OS-agnostic) ─────────────────
|
|
# On VM-backed hosts (macOS OrbStack / Docker Desktop) the container can't
|
|
# reach the host's directly-attached LAN peers by default. The entrypoint
|
|
# then sets up the host as an SSH jump (use the `dssh` alias). Reach the host
|
|
# with `dssh host`; for named LAN peers put `ProxyJump host` overrides in a
|
|
# host-owned ~/.config/devbox-shell/ssh-lan.conf (bind-mounted in) rather than
|
|
# editing ~/.ssh/config. On native Linux Docker the LAN is reachable directly
|
|
# and this is a no-op.
|
|
# See the opencode-devbox README for the full walkthrough.
|
|
#
|
|
# DEVBOX_LAN_ACCESS: auto (default) | jump | off
|
|
# DEVBOX_LAN_ACCESS=auto
|
|
# HOST_SSH_USER: your username on the host (required for the jump). On first
|
|
# start the entrypoint prints the public key to authorize on the host.
|
|
# HOST_SSH_USER=
|
|
# DEVBOX_HOST_ALIAS: host hostname to reach (default host.docker.internal).
|
|
# DEVBOX_HOST_ALIAS=host.docker.internal
|
|
# DEVBOX_LAN_AUTOJUMP_PRIVATE: 1 = ProxyJump any private (RFC1918) IP through
|
|
# the host, so bare `dssh user@<ip>` works on whatever LAN you're roaming on.
|
|
# DEVBOX_LAN_AUTOJUMP_PRIVATE=0
|
|
|
|
# ── pi-atelier (TUI sidebar) ─────────────────────────────────────────
|
|
# The image vendors pi-atelier at a pinned, audited tag and registers it on
|
|
# container start. Set to 0 to opt out: the entrypoint then removes it from
|
|
# pi's `packages[]` instead of registering it. This lives here rather than
|
|
# being a `pi uninstall` because a broken TUI extension's failure mode is
|
|
# "pi will not start", which you cannot fix from inside pi.
|
|
# DEVBOX_ATELIER=1
|
|
|
|
# ── Git Configuration ────────────────────────────────────────────────
|
|
# Set BOTH. If unset, every repo inside the container fails with
|
|
# "Author identity unknown" on first commit, and an agent asked to commit
|
|
# will guess an identity from git log — often the wrong one. The e-mail is
|
|
# per-machine (work machines use the corporate address, personal machines the
|
|
# private one), so it belongs in this per-machine .env, never in a skill or a
|
|
# repo-local override. Consumed by entrypoint-user.sh -> ~/.gitconfig, which is
|
|
# NOT persistent across container recreate — this file is the source of truth.
|
|
GIT_USER_NAME=
|
|
GIT_USER_EMAIL=
|
|
|
|
# ── Gitea (for gitea-mcp MCP server) ────────────────────────────────
|
|
# GITEA_ACCESS_TOKEN=
|
|
# GITEA_HOST=https://gitea.example.com
|
|
|
|
# ── GitHub (optional, for GitHub MCP / git operations) ───────────────
|
|
# GITHUB_PERSONAL_ACCESS_TOKEN=
|
|
|
|
# ── AWS (optional, for AWS CLI / Bedrock) ────────────────────────────
|
|
# AWS_REGION=eu-west-1
|
|
# AWS_PROFILE=default
|
|
# AWS_ACCESS_KEY_ID=
|
|
# AWS_SECRET_ACCESS_KEY=
|
|
|
|
# ── Skillset (agent skills and instructions) ─────────────────────────
|
|
# If you have a skillset repo, the entrypoint auto-deploys skills and
|
|
# instructions on container start using relative symlinks.
|
|
# Detection is automatic if the skillset lives at WORKSPACE_PATH/skillset.
|
|
# SKILLSET_CONTAINER_PATH=
|
|
|
|
# ── Locale ───────────────────────────────────────────────────────────
|
|
# LANG=sv_SE.UTF-8
|
|
# LANGUAGE=sv_SE:sv
|
|
# LC_ALL=sv_SE.UTF-8
|