History

Per-checkout portless name for the dev server

Every checkout registered the dev server as the same portless name on the machine-shared multiplex proxy, so the proxy's duplicate-app selector listed every parallel checkout's server under one host — and its per-entry Kill button SIGTERMed whichever sibling you clicked. The name now derives from the checkout directory, scoping the selector (and its Kill button) to that checkout's own processes.

Rhys Sullivan committed 2 months ago

Commit c48a1ea1 parent 8ebd2a61 file · +1 −1Browse files

Unified · Split

apps/local/package.json+1−1
@@ -10,7 +10,7 @@ · 9 unmodified lines
1010 "scripts": {
1111 "dev": "bun run dev:proxy && bun run dev:vite",
1212 "dev:proxy": "portless proxy start --multiplex --port 1355 || true",
13− "dev:vite": "EXECUTOR_DATA_DIR=${EXECUTOR_DATA_DIR:-.executor-dev} portless --name executor-local bunx --bun vite dev",
13+ "dev:vite": "EXECUTOR_DATA_DIR=${EXECUTOR_DATA_DIR:-.executor-dev} portless --name \"executor-local-$(basename \"$(cd ../.. && pwd)\")\" bunx --bun vite dev",
1414 "build": "turbo run build --filter @executor-js/vite-plugin && bunx --bun vite build",
1515 "start": "bun run src/serve.ts",
1616 "db:generate": "drizzle-kit generate",

Keyboard shortcuts

General

Show keyboard shortcuts
?
Focus the current search
/

Issues and pull requests

Open filters
f

Issues, pull requests and Inbox

Select next item
j↓
Select previous item
k↑
Open selected item
Enter
Dismiss filters or clear selection
Esc

Repository code

Go to file
t