Skip to content

Deploy via Vercel with multi-zone path rewrites#1

Merged
ivanbanov merged 1 commit into
mainfrom
deploy/vercel-multizone
Jun 24, 2026
Merged

Deploy via Vercel with multi-zone path rewrites#1
ivanbanov merged 1 commit into
mainfrom
deploy/vercel-multizone

Conversation

@ivanbanov

Copy link
Copy Markdown
Contributor

Sets up production deployment on Vercel with a multi-zone routing layer.

What this does

  • Adds vercel.json:
    • serves the static src/ site at the apex (dunky.dev)
    • transparently proxies /state-machine/* to the independently-deployed dunky-state-machine project — sub-apps keep their own repo/CI/deploy cadence (true multi-zone)
    • cleanUrls for extensionless paths
  • Removes the unused GitHub Pages deploy.yml (had stale TODO placeholders and would compete with Vercel). ci.yml (lint + typecheck) stays.

Follow-up (Vercel dashboard, not in this PR)

  1. Import this repo as a Vercel project.
  2. Move www.dunky.dev (primary) + dunky.dev (308 → www) from the dunky-state-machine project onto this website project.
  3. Keep dunky-state-machine.vercel.app attached to state-machine — the proxy targets it.

🤖 Generated with Claude Code

Add vercel.json: serve the static src/ site at the apex and proxy
/state-machine/* to the independently-deployed dunky-state-machine
project. Drop the unused GitHub Pages deploy workflow.

Co-authored-by: Claude <noreply@anthropic.com>
@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dunky Ready Ready Preview, Comment Jun 24, 2026 11:11am

@ivanbanov ivanbanov merged commit 598cfee into main Jun 24, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant