| name | devops |
| description | Deploy to Vercel (frontends, serverless), Railway (backends, services), Supabase (database, auth, storage), GitHub Actions CI/CD. Use for deployments, infrastructure, monitoring, CI/CD. |
| license | MIT |
| version | 3.0.0 |
DevOps Skill
Deploy and manage cloud infrastructure across Vercel, Railway, Supabase, and GitHub Actions.
When to Use
- Deploy frontends and serverless functions to Vercel
- Deploy backend services to Railway
- Manage databases, auth, and storage with Supabase
- Set up CI/CD pipelines with GitHub Actions
- Monitor deployments and debug production issues
- Manage environment variables and secrets
Platform Selection
| Need | Choose |
|---|
| Frontend / Next.js / static sites | Vercel |
| Serverless API routes / edge functions | Vercel |
| Long-running backend services | Railway |
| Background workers / cron jobs | Railway |
| PostgreSQL database | Supabase |
| User authentication | Supabase Auth |
| File/image storage | Supabase Storage |
| Realtime subscriptions | Supabase Realtime |
| Edge functions (Deno) | Supabase Edge Functions |
| CI/CD pipelines | GitHub Actions |
Quick Start
vercel deploy
vercel deploy --prod
railway up
railway logs
supabase db push
supabase migration new feat_name
gh workflow run deploy.yml
gh run list
Command Reference
Vercel
vercel deploy
vercel deploy --prod
vercel ls
vercel inspect <url>
vercel logs <url>
vercel redeploy
vercel env pull .env.local
vercel env add SECRET_KEY
vercel env rm SECRET_KEY
vercel link
vercel project ls
vercel domains add example.com
vercel domains ls
Railway
railway up
railway up --detach
railway logs
railway logs --tail
railway status
railway variables
railway variables set KEY=VALUE
railway variables get KEY
railway service
railway open
railway connect postgres
Supabase
supabase db push
supabase db reset
supabase migration new <name>
supabase migration list
supabase functions deploy <name>
supabase functions serve
supabase functions list
supabase auth list
supabase storage create <bucket>
supabase link --project-ref <ref>
supabase db diff
supabase gen types typescript
GitHub Actions
gh workflow list
gh workflow run <name>
gh run list
gh run view <id>
gh run view <id> --log
gh run watch
gh secret set SECRET_KEY
gh secret list
Best Practices
Security: Never commit .env files, use platform-managed secrets, rotate keys regularly, use Supabase RLS policies
Performance: Use Vercel edge caching, Railway health checks, Supabase connection pooling (pgBouncer)
Cost: Stay on free tiers when possible, monitor usage in platform dashboards, use preview deployments to test before prod
Development: Use vercel dev / supabase start for local development, branch deploys for PRs
Safety Guardrails
NEVER do these:
vercel remove / vercel project rm -- deletes the project
railway delete -- deletes the service
supabase db reset on production -- destroys all data
- Commit secrets to git -- use platform env vars instead
ALWAYS do these:
- Test on preview/staging before production
- Use migrations for database changes (never raw SQL on prod)
- Keep deployment logs for debugging
- Set up health check endpoints
Resources