Skip to content

Configure Vercel deployment for token migration development - #9

Draft
VegeBun-csj wants to merge 2 commits into
dora-migrate-votafrom
codex/vercel-migration-dev
Draft

VegeBun-csj wants to merge 2 commits into
dora-migrate-votafrom
codex/vercel-migration-dev

Conversation

@VegeBun-csj

@VegeBun-csj VegeBun-csj commented Sep 22, 2026

Copy link
Copy Markdown
Collaborator

Enable source deployment of the dora-migrate-vota branch to the Dora Factory Vercel project vota-migration-dev. Adds Vite SPA routing, Node 24, a pinned pnpm install/build, an environment template, and deployment documentation. A separate pull-request workflow checks the Vercel build while the existing Docker/ECR/EKS deployment remains active.

Validation: clean pnpm@8.6.6 install --frozen-lockfile and pnpm run build passed locally on Node 24 with the active configuration recovered from the existing published site. Both hosted deployments are READY. Homepage, consent and wallet-selection dialogs, and hash-based legal pages render. RPC chain IDs and token/bridge bytecode queries passed; all active build-variable values match the existing published sites. No signing or migration transaction was performed. No application logic, contract addresses, or DNS records are changed by this PR.

Hosted verification is complete; this draft records the staged migration before Git integration and domain cutover. Git automatic deployment still needs the Vercel GitHub App to be granted access to this repository. Domain cutover and retirement of EKS are separate steps.

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