Setup Guide

Required Steps

Get Your API Keys

BoDiGi 2.0 needs a few API keys to work. This guide walks you through getting each one, keeping them safe, and deploying your first app with real results.

Keeping Your Keys Safe

Never commit keys to git

API keys in code get pushed to GitHub and can be stolen by bots within minutes. Always use environment variables.

Use .env.local for local dev

Create a .env.local file (already in .gitignore) for local development. Never commit it.

Use env vars in production

Set keys in your hosting platform's dashboard (Vercel, Netlify, etc.) — never in code or config files.

Rotate keys if exposed

If a key ever appears in a commit, screenshot, or public URL — revoke it immediately and generate a new one.

How to Add Your Keys
1

Local Development

Create a .env.local file in the project root with your keys. This file is already in .gitignore so it won't be committed.

2

Production (Vercel)

Go to your Vercel project → Settings → Environment Variables → add each key. They're encrypted and never exposed in code.

3

Other Platforms

Netlify: Site Settings → Environment Variables. Railway: Variables tab. Docker: Use -e flags or docker-compose environment section.

Got your keys configured?