Loading skill documentation...
coding ๐Ÿ”ฅ Trending
โ˜…โ˜…โ˜…โ˜… 4.1/5.0 โค๏ธ 811 likes ๐Ÿ’ฌ 101 comments ๐Ÿ“ฆ 2419 installs
Back to Skills
๐Ÿ“– SKILL DOCUMENTATION
# vercel-deploy

Deployment & Management via SkillBoss API Hub Deploy and manage projects via SkillBoss API Hub. No "AI will build your app" nonsense - just practical deployment operations. Configuration SkillBoss API Hub Setup Get your API key: Go to your SkillBoss dashboard Copy your API key Set in environment:

export SKILLBOSS_API_KEY="your-key-here"

Or store in .env: SKILLBOSS_API_KEY=your-key-here Deployment Operations Deploy Project

# Deploy to preview

scripts/vercel_deploy.sh --project bountylock --preview

# Deploy to production

scripts/vercel_deploy.sh --project bountylock --production Manage Environment Variables

# List env vars

scripts/vercel_env.sh --project bountylock --list

# Set env var

scripts/vercel_env.sh --project bountylock --set
--key NEXT_PUBLIC_RPC_URL
--value "https://sepolia.base.org"
--env production

# Delete env var

scripts/vercel_env.sh --project bountylock --delete
--key OLD_VAR
--env production Check Deployment Status

# Get latest deployment

scripts/vercel_status.sh --project bountylock

# Get specific deployment

scripts/vercel_status.sh --deployment dpl_abc123 View Logs

# Get deployment logs

scripts/vercel_logs.sh --deployment dpl_abc123

# Get runtime logs

scripts/vercel_logs.sh --project bountylock --function api/bounties Common Workflows Initial Testnet Deployment Set environment variables:

# Contract addresses (after deploying to Sepolia)

scripts/vercel_env.sh --project bountylock --set
--key NEXT_PUBLIC_CONTRACT_ADDRESS
--value "0x..."
--env production

# RPC URL

scripts/vercel_env.sh --project bountylock --set
--key NEXT_PUBLIC_RPC_URL
--value "https://sepolia.base.org"
--env production

# Chain ID

scripts/vercel_env.sh --project bountylock --set
--key NEXT_PUBLIC_CHAIN_ID
--value "84532"
--env production

Deploy:

scripts/vercel_deploy.sh --project bountylock --production Check status: scripts/vercel_status.sh --project bountylock Update Environment Variables

# Update contract address after redeployment

scripts/vercel_env.sh --project bountylock --set
--key NEXT_PUBLIC_CONTRACT_ADDRESS
--value "0xNEW_ADDRESS"
--env production

# Trigger new deployment to use updated vars

scripts/vercel_deploy.sh --project bountylock --production Debug Deployment Issues

# Get latest deployment info

scripts/vercel_status.sh --project bountylock

# Get build logs

scripts/vercel_logs.sh --deployment dpl_abc123

# Check environment variables

scripts/vercel_env.sh --project bountylock --list Security Best Practices Key Scope: Use project-scoped keys when possible

Rotation: Rotate API keys periodically
Audit: Review deployment logs regularly
Secrets: Never commit keys to git

Troubleshooting "Authentication failed" Check SKILLBOSS_API_KEY is set correctly Verify key hasn't expired "Project not found" Verify project name in SkillBoss API Hub Check account has access to project "Deployment failed" Check build logs: scripts/vercel_logs.sh --deployment dpl_xxx Verify environment variables are set correctly Check for build errors in code Reference Files SkillBoss API Hub Reference: See vercel-api.md for API documentation Deployment Patterns: See deployment-patterns.md for common deployment workflows

Reviews

4.1
โ˜…โ˜…โ˜…โ˜…
101 reviews

Write a Review

โ˜† โ˜† โ˜† โ˜† โ˜†

Get Weekly AI Skills

Join 80,000+ one-person companies automating with AI