Deploy MaterialScope on Vercel via container service (reuses Docker contract) - #26
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
materialscope | 3f79193 | Aug 30 2026, 06:11 PM |
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
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
Adds the minimal Vercel deployment seam so MaterialScope can run on Vercel Hobby (free) as a demo target for feedback, without touching the existing Docker deployment contract.
materialscopeservice withroot: ".",runtime: "container",entrypoint: "Dockerfile", plus a catch-all rewrite/(.*)routing all public traffic to that service. Vercel builds the existing rootDockerfile(Chromium, Kaleido, Dash/FastAPI combined server), stores it in the Vercel Container Registry, and serves it as an autoscaling Function on Fluid compute (scale-to-zero after 5 min idle).test_vercel_seam_reuses_docker_contractasserts the seam reuses the real Dockerfile (noDockerfile.vercelcopy, no duplicated Docker contract) and exposes exactly one service via a single catch-all rewrite.What is intentionally NOT changed
Dockerfile,docker/start.sh,requirements.txt, pyproject packaging contract, and all application logic remain untouched.api/index.py, no serverless runtime, no static shell — the full Dash/FastAPI app runs inside the container as today.docker/start.shalready binds0.0.0.0:${PORT:-8050}, satisfying Vercel's$PORTcontract with zero changes.Verification
ruff check .cleantests/test_deployment_contract.py: 8/8 passedOperational notes (demo scope)