Skip to content

History / Installation wslc

Revisions

  • fix(wiki): make wslc PowerShell scripts ANSI-safe and re-runnable Two problems in the Installation-wslc guide's copy-paste PowerShell: - Replace em/en dashes inside the powershell code fences with ASCII hyphens (two Write-Host strings + two comments). Saved to a .ps1 and read as Windows-1252, the UTF-8 dash bytes were mangling output. - Under $ErrorActionPreference = "Stop", native wslc stderr writes are promoted to terminating errors, so a re-run aborted at `wslc network create` ("already exists"), and `container rm` had the same latent bug. Wrap both idempotent calls in try/catch, and route the `run` calls through an Invoke-Wslc helper that tolerates benign stderr (e.g. first-run pull progress) but still fails on a non-zero exit code. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @smeeks-swo smeeks-swo committed Jul 4, 2026
  • docs(wiki): add stop-foreman-wslc.ps1 to the wslc page Add a stop script alongside the start/update scripts: stops the three containers by default, with a -Remove switch to also delete them. Uses SilentlyContinue so stopping an already-stopped container doesn't error; data on the C:\foreman bind mounts is preserved either way. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @StuartMeeks StuartMeeks committed Jul 4, 2026
  • docs(wiki): add update-foreman-wslc.ps1 to the wslc page Add a second optional script that pulls the latest published images and recreates the stack against them by reusing start-foreman-wslc.ps1 (which removes the old containers first). Data on the C:\foreman bind mounts is preserved; note that a newer ff-server may run additive DB migrations on next start. Confirmed `wslc image pull` exists via `wslc image --help`. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @StuartMeeks StuartMeeks committed Jul 4, 2026
  • docs(wiki): wslc page — verified, with real expected-output examples Mark the WSL Containers path as tested end-to-end on the preview and add anonymised sample output at the key checkpoints: network list (bridge driver), sf-mcp /health, the ff-server "Connected to MCP server" log line (cross-container name DNS), and container list. Document two preview gaps found while testing: wslc ignores image HEALTHCHECKs (no health column / no State.Health), so verify via /health curls; and add a cmd-vs-PowerShell shell note (backtick continuation is PowerShell-only). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @StuartMeeks StuartMeeks committed Jul 4, 2026
  • docs(wiki): split Installation into Docker and WSL Containers (wslc) pages Turn the single Installation page into a landing/chooser page with two children: Installation-Docker (the existing Docker Compose instructions, migrated) and a new Installation-wslc runbook for running the stack under WSL's native `wslc` container runtime without Docker Desktop. The wslc page translates compose.yaml into individual `wslc run` commands on a shared user-defined network (the ff-server->sf-mcp and ff-client->ff-server hops resolve by container name), uses Windows bind mounts for persistence, and flags the preview features it relies on (network DNS, named volumes, restart) with a host-gateway fallback. Nest both under Installation in the sidebar. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

    @StuartMeeks StuartMeeks committed Jul 4, 2026