garaje 0.1.5 → 0.2.0

package/templates/pi/Dockerfile

@@ -21,6 +21,54 @@ RUN apt-get update && apt-get install -y --no-install-recommends \
     && apt-get update && apt-get install -y --no-install-recommends gh docker-ce-cli docker-buildx-plugin docker-compose-plugin \
     && rm -rf /var/lib/apt/lists/*
 
+# --- Per-bay toolchains -------------------------------------------------------
+# GENERATED by `garaje park` from every parked bay's recipe.yaml — the same
+# declaration the bay images build from. The agent's container therefore carries
+# exactly the runtimes of the code it edits, which is what lets pi-lens spawn a
+# language server and a linter per bay.
+#
+# These layers sit BEFORE the pi/npm layers on purpose. Docker invalidates every
+# layer after a changed one; Ruby compiles from source under mise (~5-10 min).
+# A PI_VERSION bump is frequent and must NOT recompile Ruby. Parking a new bay
+# is rare, and may legitimately pay that recompile cost.
+COPY toolchain/ /tmp/toolchain/
+
+# The apt list is a bare, newline-separated file (no comments — xargs would read
+# a '#' line as a package name). Empty for a garaje with no bays, hence the -s test.
+RUN if [ -s /tmp/toolchain/apt-packages.txt ]; then \
+        apt-get update \
+        && xargs -a /tmp/toolchain/apt-packages.txt \
+             apt-get install -y --no-install-recommends \
+        && rm -rf /var/lib/apt/lists/*; \
+    fi
+
+# mise in SHIMS mode. A shim resolves its tool's version from the CALLING
+# directory — and pi-lens spawns language servers with cwd = the bay root. So
+# each bay's own .ruby-version selects its runtime with zero integration code,
+# and two bays on different Ruby versions each get the right one.
+ENV MISE_DATA_DIR=/root/.local/share/mise
+ENV PATH=/root/.local/share/mise/shims:/root/.local/bin:$PATH
+
+# Pinned for build reproducibility: an unpinned installer means two teammates
+# who build a month apart get different mise versions — not theoretical, this
+# exact version's install already warns "precompiled ruby will be the default
+# in 2026.8.0". Bump deliberately, matching PI_VERSION's own pinning discipline.
+ARG MISE_VERSION=2026.7.5
+RUN export MISE_VERSION="${MISE_VERSION}" \
+    && curl -fsSL https://mise.run | sh \
+    && mkdir -p /root/.config/mise \
+    && cp /tmp/toolchain/mise.toml /root/.config/mise/config.toml \
+    && mise install --yes \
+    && mise reshim \
+    && rm -rf /tmp/toolchain
+
+# pi-side project dependencies live on the pi-deps volume (compose.framework.yaml).
+# ONE shared BUNDLE_PATH serves EVERY bay: bundler namespaces gems by Ruby ABI
+# directory and activates strictly from the calling project's Gemfile.lock. So
+# `bundle exec rubocop` in bays/rtfm gets rtfm's pinned cops and cannot see
+# stacey's gems. Verified against ruby:3.4-slim — see the design spec §2.
+ENV BUNDLE_PATH=/garaje/deps/bundle
+
 # Pi version is pinned in pi/PI_VERSION so a pi bump is a one-file diff
 # teammates pick up on `git pull && garaje up --build`. Bring the file in first
 # as its own layer so editing it busts the cache for the npm install layer

package/templates/pi/toolchain/mise.toml

@@ -0,0 +1,14 @@
+# GENERATED by `garaje park` from bays/*/recipe.yaml. Do not edit by hand.
+#
+# The union of every parked bay's declared runtimes. mise installs all of
+# them; each bay's own .ruby-version / .node-version then selects which one
+# applies inside that bay. pi-lens spawns language servers with cwd = the bay
+# root, so the mise shim on PATH resolves the right version with no glue.
+#
+# bays: (none)
+
+[tools]
+
+[settings]
+# Honor each bay's .ruby-version / .node-version (they already ship them).
+idiomatic_version_file_enable_tools = ["node", "ruby"]