## Parent: #475 ## Summary Operator tasks that must be done manually before or during the deployment process. ## Tasks ### Before deployment - [x] **Vercel**: Create Vercel project, get `VERCEL_TOKEN`, `VERCEL_ORG_ID`, `VERCEL_PROJECT_ID` - [x] **Vercel**: Add all env vars from `.env.example` to Vercel project settings - [x] **GitHub Secrets**: Add `VERCEL_TOKEN`, `VERCEL_ORG_ID`, `VERCEL_PROJECT_ID` to GitHub repo secrets - [x] **DNS**: Point `plotlink.xyz` DNS to Vercel (A/CNAME records as instructed by Vercel) ### After initial deployment - [x] **Farcaster**: Sign account association with custody key for `plotlink.xyz` domain — fill `accountAssociation` in `public/.well-known/farcaster.json` - [x] **Base.dev**: Register PlotLink app at base.dev — get `base:app_id` - [x] **Base.dev**: Fill metadata (icons, tagline, description, screenshots) in dashboard - [x] **Builder Code**: Register at base.dev to get builder code — set `NEXT_PUBLIC_BUILDER_CODE` env var - [x] **Screenshots**: Take 3 screenshots of the live app for Farcaster manifest `screenshotUrls` ## Acceptance Criteria - [x] `plotlink.xyz` resolves to Vercel deployment - [x] All secrets configured in GitHub Actions - [x] Farcaster account association signed - [x] Base.dev registration complete - [x] Builder code active and env var set
Parent: #475
Summary
Operator tasks that must be done manually before or during the deployment process.
Tasks
Before deployment
VERCEL_TOKEN,VERCEL_ORG_ID,VERCEL_PROJECT_ID.env.exampleto Vercel project settingsVERCEL_TOKEN,VERCEL_ORG_ID,VERCEL_PROJECT_IDto GitHub repo secretsplotlink.xyzDNS to Vercel (A/CNAME records as instructed by Vercel)After initial deployment
plotlink.xyzdomain — fillaccountAssociationinpublic/.well-known/farcaster.jsonbase:app_idNEXT_PUBLIC_BUILDER_CODEenv varscreenshotUrlsAcceptance Criteria
plotlink.xyzresolves to Vercel deployment