From 9e237802f6e61cd83b72c9faa4438e6524bc5e85 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?V=C3=ADctor=20Falc=C3=B3n?= Date: Tue, 14 Jul 2026 23:38:11 +0200 Subject: [PATCH] docs: document running the dev server for QA (#677) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit ## What Adds a "Running the server for QA" subsection to the project `CLAUDE.md` so commands/skills that ask the user to open the app in Chrome have clear, project-level steps. ## Steps documented 1. First run in a worktree? Prepare it with `./worktree.sh `. 2. Start the server if it isn't running: `composer run dev`. 3. Get the dynamic per-worktree URL — `composer run dev` prints and copies it to the clipboard on startup; don't guess it. Docs-only change. --- CLAUDE.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index a011ea9f..598ad3de 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -15,6 +15,14 @@ composer run dev # Start full dev environment (PHP server, queue, Vite, bun run dev # Vite dev server only ``` +### Running the server for QA + +When a command or skill needs the user to open the app in Chrome to review a change: + +1. **First run in a worktree?** Prepare it: `./worktree.sh /path/to/main/repo` (copies `.env` + `storage/keys`, installs `bun` and `composer` deps). Skip if already set up. +2. **Start the server** if it isn't running: `composer run dev`. +3. **Get the URL** — it's dynamic per worktree, so don't guess it. On startup `composer run dev` prints and copies it to the clipboard (`✓ copied to clipboard`); read it from the `server` pane output. Ask the user to open that URL in Chrome to QA. + ### Build & Quality ```bash