v1.18.0-wsl2.4

What's changed

Documentation

• Added install/update/uninstall instructions with step-by-step PATH setup
• Added "About This Fork" section explaining the project's history and maintenance
• Clarified requirements and added release badge for easy binary discovery

Upstream sync

• Merged latest upstream roots/trellis-cli changes (dependency bumps, CI updates, README updates)
• No changes to WSL-specific code — all existing functionality carries forward

Install

1. Download trellis.exe and trellis-linux from below
2. Place both in a folder (e.g., C:\trellis-wsl\)
3. Add to PATH:

   $userPath = [Environment]::GetEnvironmentVariable("Path", "User")
   [Environment]::SetEnvironmentVariable("Path", $userPath + ";C:\trellis-wsl", "User")

4. Restart your terminal, then: trellis vm start

See the README for full details.

Full changelog: v1.18.0-wsl2.3...v1.18.0-wsl2.4

v1.18.0-wsl2.3 - UX improvements and upstream-ready CLI install

What's new

• trellis init on Windows - now shows a clear message explaining that the WSL backend manages dependencies (Python, Ansible, etc.) automatically inside the VM, instead of failing with a virtualenv error.
• Improved guard messages - commands that must be run from Windows PowerShell (e.g. trellis vm start) now echo back the exact command to run, making the guidance more actionable.
• trellis vm open and trellis vm sync from WSL - previously showed a confusing "only supported on Windows (WSL2)" error when run from inside WSL. Now correctly says "Run 'trellis vm open' from Windows PowerShell" like the other VM commands.
• Bootstrap CLI install is now upstream-ready - trellis is installed inside the distro during bootstrap. Uses the local trellis-linux binary if present (dev/fork builds), otherwise falls back to the official install script for upstream releases.

Note: This is a pre-release fork build for testing. The upstream PR is open at roots#667.

How to update

1. Download both trellis.exe and trellis-linux below
2. Replace both files in your existing install directory (e.g., C:\trellis-wsl\)

Important: Both binaries must be in the same directory. The Windows binary copies trellis-linux into WSL distros during bootstrap.

Assets

• trellis.exe - Windows binary
• trellis-linux - Linux binary (for WSL distros)

Previous releases

• v1.18.0-wsl2.2 - Fixed vm start silently deleting existing provisioned distros
• v1.18.0-wsl2.1 - Initial WSL2 backend release

v1.18.0-wsl2.2

Bug fix

Fixed vm start silently deleting provisioned WSL distros. The previous
release relied solely on an external marker file to determine if a distro was
fully provisioned. Distros set up before the marker system existed were
incorrectly flagged as unprovisioned and deleted without warning.

Changes:

• isProvisioned() now falls back to checking /etc/trellis-project-root
  inside the distro before concluding it's unprovisioned. Self-heals the marker
  file on success.
• vm start now prompts for confirmation before deleting a distro that appears
  unprovisioned, instead of silently deleting it.

Also includes golangci-lint fixes from the previous commit (no behavior change).

How to update

1. Download both trellis.exe and trellis-linux below
2. Replace both files in your existing install directory (e.g., C:\trellis-wsl\)

Important: Both binaries must be in the same directory. The Windows binary
copies trellis-linux into WSL distros during bootstrap.

Assets

• trellis.exe — Windows binary
• trellis-linux — Linux binary (for WSL distros)

v1.18.0-wsl2.1 - Native WSL2 VM Backend for Windows

What's New

First release of the WSL2 VM backend fork. It adds a native WSL2-based vm.Manager implementation to trellis-cli, giving Windows developers a first-class trellis vm experience without Lima, Vagrant, or VirtualBox.

Quick Start

1. Download both binaries below (trellis.exe and trellis-linux)
2. Place them in the same directory (e.g., C:\trellis-wsl\)
3. cd into any existing Trellis project, or create a new one:

   C:\trellis-wsl\trellis.exe new example.com
   cd example.com
   

4. Start the VM:

   C:\trellis-wsl\trellis.exe vm start
   

Important: Both binaries must be in the same directory. trellis.exe runs on Windows; trellis-linux is automatically copied into WSL2 distros during bootstrap. WSL2 is auto-detected on Windows — no config changes needed.

Requirements

• Windows 10/11 with WSL2 enabled
• No other dependencies needed (Python, Ansible, Node.js are installed automatically inside the distro)

What works

• trellis vm start — Creates and provisions a dedicated WSL2 distro per project
• trellis vm stop — Syncs config changes back to Windows, then stops the distro
• trellis vm delete — Removes the distro and all its data
• trellis vm shell — Opens an interactive shell inside the distro
• trellis vm open — Opens VS Code connected to the WSL distro
• trellis vm sync — Manual config sync from WSL back to Windows
• trellis vm trust — Imports SSL certs into the Windows trust store
• trellis provision development — Runs Ansible provisioning inside WSL
• trellis deploy — Deploys from inside WSL
• trellis db open — Opens TablePlus with direct MySQL connection

Known limitations

• One project at a time — WSL2 distros share a network namespace, so only one can run services at a time
• Windows-only — macOS/Linux users should continue using Lima

Based on roots/trellis-cli v1.18.0 (commit 07e51b4).

Full details: #1