Environment Variables

Required Variables

These variables must be set for the site to function. Copy them from your Handover project dashboard.

# Handover API connection
NEXT_PUBLIC_HANDOVER_API_URL=https://handover.your-platform.com
NEXT_PUBLIC_HANDOVER_API_KEY=ho_live_your_project_key_here

API Key Format

API keys have a specific format to indicate environment. Always use live keys for production deployments.

• Live keys: ho_live_[uuid] - for production sites
• Test keys: ho_test_[uuid] - for development/staging
• Keys are generated when you create a project
• Regenerate keys if compromised

Branding Variables (Optional)

Customize the admin interface and site metadata per client. All branding variables are optional and have sensible defaults.

# Site branding
NEXT_PUBLIC_SITE_NAME="Acme Corp Website"
NEXT_PUBLIC_ADMIN_TITLE="Acme Admin Dashboard"
NEXT_PUBLIC_BRAND_TAGLINE="Keep your content fresh..."
NEXT_PUBLIC_SUPPORT_EMAIL="support@acmecorp.com"

Security Best Practices

Follow these guidelines to keep your configuration secure.

• Never commit .env.local to version control
• Add .env.local to .gitignore
• Use different API keys for staging and production
• Rotate API keys when team members leave
• Store production env vars in hosting platform securely

Vercel/Netlify Setup

When deploying to hosting platforms, add environment variables through their dashboard rather than committing them.

# Vercel CLI
vercel env add NEXT_PUBLIC_HANDOVER_API_URL
vercel env add NEXT_PUBLIC_HANDOVER_API_KEY

# Or use dashboard: Settings > Environment Variables