[claude] Add vortex-bench-server v3 deployment infrastructure#7644
Merged
connortsui20 merged 3 commits intoct/benchmarks-v3from Apr 26, 2026
Merged
[claude] Add vortex-bench-server v3 deployment infrastructure#7644connortsui20 merged 3 commits intoct/benchmarks-v3from
connortsui20 merged 3 commits intoct/benchmarks-v3from
Conversation
… backup Adds the deployment artifacts for vortex-bench-server alongside the existing v2 site. Dual-write only — does not modify v2 service or route DNS. Manual EC2 setup steps documented in ec2-init.txt. Per orchestrator direction the daily DuckDB backup is a host-side cron + script (benchmarks-website/server/scripts/backup.sh) rather than a GitHub Actions workflow, avoiding new SSH or IAM surface area for what is currently a convenience backup. Signed-off-by: Claude <noreply@anthropic.com>
…ealth path - Runtime stage of the server Dockerfile now installs the matching DuckDB CLI binary so backup.sh's `docker exec ... duckdb ...` works. Pinned via `ARG DUCKDB_VERSION=1.4.1` to track libduckdb-sys in Cargo.lock; unzip/wget are apt-purged to keep the image small. - ec2-init.txt smoke-check uses /health (the actual route in benchmarks-website/server/src/app.rs:61), not /healthz. Signed-off-by: Claude <noreply@anthropic.com>
connortsui20
changed the title
…all matching CLI, fix /health path - benchmarks-website/server/Cargo.toml: bump duckdb-rs to 1.10502 (engine 1.5.2) to match vortex-duckdb's bundled engine pin in vortex-duckdb/build.rs:386. Cargo.lock regenerated; cargo test -p vortex-bench-server and cargo clippy -p vortex-bench-server --all-targets pass clean. - benchmarks-website/server/Dockerfile: ARG DUCKDB_VERSION bumped to 1.5.2 to match the resolved libduckdb-sys version. The runtime stage still installs the matching CLI via wget+unzip with apt-purge cleanup. - benchmarks-website/ec2-init.txt: smoke-check and rotation verification both use /health (the actual route in benchmarks-website/server/src/app.rs:61), not /healthz. Signed-off-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces the deployment infrastructure for vortex-bench-server v3, a new benchmarking server that runs alongside the existing v2 instance. The v3 server provides an ingest endpoint for benchmark results with bearer token authentication and uses DuckDB for data storage.
Changes included:
GitHub Actions workflow (
publish-bench-server.yml): New CI pipeline that builds and publishes the vortex-bench-server Docker image to GHCR on changes to the server code, vortex-bench crate, or Cargo.lock.Dockerfile (
benchmarks-website/server/Dockerfile): Multi-stage Docker build that:Backup script (
benchmarks-website/server/scripts/backup.sh): Daily backup utility that:vortex-ci-benchmark-results/v3-backups/)Docker Compose configuration: Added vortex-bench-server service that:
/etc/vortex-bench/secrets.envEC2 initialization guide (
ec2-init.txt): Comprehensive setup documentation covering:The v3 server is designed to run additively alongside v2, allowing for gradual DNS migration and dual-write support from CI.
Testing
The Docker image build is validated by the GitHub Actions workflow on each push to develop. The backup script can be tested manually on the EC2 host before cron scheduling. Smoke tests are documented in the setup guide (curl against
/healthendpoint on port 3001).https://claude.ai/code/session_019mBcBdF4LhKDXyKwuKRAPV