Deployment Guide
Prerequisites
- Node.js 20+
- A Supabase project
- A Lingo.dev API key
- A Vercel account (for deployment)
- A GitHub account (for CI/CD)
Step 1: Supabase Setup
- Create a new project at supabase.com
- Go to the SQL Editor
- Run the SQL from
lib/supabase.ts(the commented section at the bottom) - Copy your project URL and keys from Settings β API
Step 2: Environment Variables
Create .env.local with your actual values:
LINGODOTDEV_API_KEY=your_key
NEXT_PUBLIC_SUPABASE_URL=https://your-project.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=your_anon_key
SUPABASE_SERVICE_ROLE_KEY=your_service_key
NEXT_PUBLIC_APP_URL=https://your-app.vercel.app
Step 3: Translate Documentation
Run the Lingo CLI to generate translations for all documentation:
npm run translate:docs
This creates translated docs in docs/es/, docs/fr/, docs/de/, docs/ja/, and docs/zh/.
Step 4: Deploy to Vercel
- Push your code to GitHub
- Go to vercel.com and import your repository
- Add all environment variables in the Vercel dashboard
- Deploy
Step 5: GitHub Actions (CI/CD)
- Go to your GitHub repo β Settings β Secrets and variables β Actions
- Add secret:
LINGODOTDEV_API_KEY - The workflow in
.github/workflows/translate-docs.ymlwill automatically translate docs on every push
Step 6: Configure Lingo MCP in Cursor
- Open Cursor Settings β MCP tab
- Add new MCP server:
- Name:
Lingo.dev - Command:
npx - Args:
["-y", "lingo.dev", "mcp", "YOUR_API_KEY"]
- Name:
- Restart Cursor
- Verify the green status indicator
Production Checklist
- Supabase tables created with RLS enabled
- All environment variables set in Vercel
- Lingo Compiler building translations on deploy
- Documentation translated via CLI
- CI/CD workflow tested
- MCP configured in development environment
- Demo data generated for showcase
- All 5 Lingo.dev tools verified working
Monitoring
After deployment, monitor your application:
- Vercel Dashboard β Deployment logs and analytics
- Supabase Dashboard β Database monitoring and logs
- GitHub Actions β CI/CD pipeline status