Local Dev Server Control

Use this skill to manage the current repository's local development server without touching unrelated Node.js processes.

Run commands from repository root: E:\coding\TermLink

Quick Start

Check current status:

powershell -ExecutionPolicy Bypass -File .\skills\local-dev-server-control\scripts\manage-local-dev-server.ps1 -Action status

Start server:

powershell -ExecutionPolicy Bypass -File .\skills\local-dev-server-control\scripts\manage-local-dev-server.ps1 -Action start

Stop server:

powershell -ExecutionPolicy Bypass -File .\skills\local-dev-server-control\scripts\manage-local-dev-server.ps1 -Action stop

Restart server:

powershell -ExecutionPolicy Bypass -File .\skills\local-dev-server-control\scripts\manage-local-dev-server.ps1 -Action restart

Behavior

1. Manage only the repo-local development chain: cmd -> npm run dev -> nodemon -> node src/server.js.
2. Default to http://127.0.0.1:3010 and set PORT=3010 when starting.
3. Write combined startup logs to logs/dev-server.log.
4. Probe /api/health after startup and treat 401 Unauthorized as a valid sign that the server is up with auth enabled.
5. Fall back to .env credentials when present, otherwise use admin/admin for authenticated health checks.

Optional Parameters

powershell -ExecutionPolicy Bypass -File .\skills\local-dev-server-control\scripts\manage-local-dev-server.ps1 `
  -Action restart `
  -BaseUrl http://127.0.0.1:3010 `
  -StartupTimeoutSec 30

Rules

1. Do not use this skill for pm2 service management; use win-server-deploy for Windows service operations.
2. Do not kill unrelated node.exe processes outside this repository.
3. Prefer -Action restart over ad hoc process killing when the request is simply to reload the local dev environment.