Avatar for the vortex-data user
vortex-data
vortex
BlogDocsChangelog

Performance History

Latest Results

benchmarks-website/ops: install.sh stages timers when env tokens are empty The install script used to `enable --now` the deploy timer, backup timer, and server unit unconditionally. On a fresh box the env file is still the template (`INGEST_BEARER_TOKEN=` empty), so: - `vortex-bench-server.service` fails startup (no ingest token). - `vortex-bench-deploy.service` may roll a build but the server it tries to restart is in a failed state. - `vortex-bench-backup.service` calls `/api/admin/snapshot` with an empty admin token, immediately gets a 503 or 404, and exits 3. Operator sees a wall of red in `journalctl` before they've finished editing the env file. Detect the empty-token case and enable the units without starting them; the "next steps" block already points at the edit-then-start path. `grep -E '^INGEST_BEARER_TOKEN=.+'` matches a non-empty value after the `=` (empty match is the template default). Same check for `ADMIN_BEARER_TOKEN`. Both must be set for the auto-start to fire. Trimmed the now-stale "wait ~90s for the first deploy-timer fire" line from the operator-next-steps block to "after starting the timers, watch the first deploy fire …" so the order is right. Signed-off-by: Connor Tsui <connor.tsui20@gmail.com>
ct/bench-v3-autopilot
3 minutes ago

Latest Branches

CodSpeed Performance Gauge
0%
Benchmarks Website V3: Admin and Auto-Deploy#7849
36 minutes ago
12be8ce
ct/bench-v3-autopilot
CodSpeed Performance Gauge
-3%
4 hours ago
1060cc7
ad/cudf
CodSpeed Performance Gauge
0%
4 hours ago
7ae710a
os/array-tree-layout
Ā© 2026 CodSpeed Technology
Home Terms Privacy Docs