sitespeed.io is not on PATH in the container -- the base image uses a
full absolute path for its ENTRYPOINT. We now run 'find' during the
Docker build, write the path to /sitespeed_env, and source it in
start.sh so SITESPEED_BIN is set before node app.js starts.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
execSync/which inside Node.js doesn't see the full container PATH.
Switching to spawn('sh', ['-c', shellCmd]) so the shell resolves
sitespeed.io exactly as the original image entrypoint does.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The path /usr/local/lib/node_modules/... does not exist in the image.
runner.js already falls back to `which sitespeed.io` automatically.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- runner.js: auto-detects sitespeed.io via which/candidates instead of
hardcoded path; collects all stderr and appends last 20 lines to the
error so the real failure is visible in the UI log
- running.pug: render multi-line error messages line-by-line
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Without Xvfb running, Chrome exits immediately with code 1.
The base sitespeedio image normally handles this via its own
entrypoint script; we now replicate that with start.sh.
Also drop --headless (breaks visual metrics) and add --disable-gpu
for stable Chrome rendering inside Docker.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Base image sitespeedio/sitespeed.io sets ENTRYPOINT=["sitespeed.io"],
causing our CMD ["node","app.js"] to be passed as args to sitespeed.io
which treated "node" as a URL to test.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
sitespeed.io web UI with Express/Pug/SQLite — port 3132.
Includes job queue, SSE live log, full metrics dashboard,
site history, CO2/axe/CWV sections, and Docker support.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
