Malin ea70d34d7f fix: don't start Xvfb in start.sh — sitespeed.io manages its own ...

Our start.sh was starting Xvfb on :99, then sitespeed.io tried to start
its own on :99, failed with exit code 1, and Chrome couldn't get a
working display. sitespeed.io is designed to manage Xvfb per test run.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-04-07 10:13:08 +02:00

routes

feat: initial Speedboard implementation

2026-04-06 19:36:13 +02:00

views

fix: surface full sitespeed.io error output + robust binary resolution

2026-04-06 19:58:17 +02:00

.gitignore

feat: initial Speedboard implementation

2026-04-06 19:36:13 +02:00

app.js

feat: initial Speedboard implementation

2026-04-06 19:36:13 +02:00

db.js

feat: initial Speedboard implementation

2026-04-06 19:36:13 +02:00

docker-compose.yml

feat: initial Speedboard implementation

2026-04-06 19:36:13 +02:00

Dockerfile

fix: discover sitespeed.js path at build time, export via /sitespeed_env

2026-04-06 20:09:29 +02:00

package.json

feat: initial Speedboard implementation

2026-04-06 19:36:13 +02:00

parser.js

feat: initial Speedboard implementation

2026-04-06 19:36:13 +02:00

queue.js

feat: initial Speedboard implementation

2026-04-06 19:36:13 +02:00

runner.js

fix: don't start Xvfb in start.sh — sitespeed.io manages its own

2026-04-07 10:13:08 +02:00

start.sh

fix: don't start Xvfb in start.sh — sitespeed.io manages its own

2026-04-07 10:13:08 +02:00

Description

No description provided

100 KiB

Languages

JavaScript 54.1%

Pug 42.2%

Dockerfile 3%

Shell 0.7%