Getting Started

Prerequisites

Ensure the following tools are installed before proceeding:

Tool	Minimum Version	Purpose
Node.js	20+	JavaScript runtime
npm	10+	Package manager (ships with Node)
Supabase CLI	latest	Local Supabase development stack
Wrangler CLI	latest	Cloudflare Pages deployment and local bindings

Tip

Install the Supabase CLI with npm install -g supabase and Wrangler with npm install -g wrangler. Authenticate Wrangler via wrangler login.

Clone and Install

git clone <repository-url> honeycomb
cd honeycomb
npm install

Environment Variables

Create a .env file in the project root. The following variables are required:

# Supabase
PUBLIC_SUPABASE_URL=           # Your Supabase project URL (e.g. https://xxxxx.supabase.co)
PUBLIC_SUPABASE_PUBLISHABLE_KEY= # Supabase anon/public key for client-side access
SUPABASE_SERVICE_ROLE_KEY=     # Supabase service role key for server-side operations

# Stripe
STRIPE_SECRET_KEY=             # Stripe secret key for server-side billing operations
STRIPE_WEBHOOK_SECRET=         # Stripe webhook signing secret for verifying events
PUBLIC_STRIPE_PUBLISHABLE_KEY= # Stripe publishable key for client-side checkout

# AI Providers
OPENAI_API_KEY=                # OpenAI API key for GPT-based features
ANTHROPIC_API_KEY=             # Anthropic API key for Claude-based features

# Third-Party Services
PUBLIC_GIPHY_API_KEY=          # Giphy API key for GIF search and display

# Internal
CRON_SECRET=                   # Shared secret for authenticating scheduled cron job endpoints

Caution

Never commit .env files to version control. The repository .gitignore should already exclude them. For production secrets, use Cloudflare Pages environment variable settings.

Running Locally

Start the development server:

npm run dev

This launches SvelteKit in development mode with hot module replacement. The app is available at http://localhost:5173 by default.

Note

If you need to test Cloudflare-specific bindings (KV, D1, etc.) locally, use wrangler pages dev instead, which wraps the SvelteKit dev server with the Cloudflare Workers runtime.

Supabase Local Setup

For a fully local development environment, spin up Supabase locally:

supabase start

This starts local instances of PostgreSQL, Auth, Storage, and the Supabase API. On first run it will pull the required Docker images.

Apply existing database migrations:

supabase db reset

This drops and recreates the local database, then applies all migrations from the supabase/migrations directory and seeds any seed data.

Create a Migration

supabase migration new <migration_name>

Creates a new empty SQL migration file in supabase/migrations/.

Diff Against Remote

supabase db diff --use-migra

Generates a migration by comparing your local schema against the current migration state.

Push to Remote

supabase db push

Applies pending local migrations to the linked remote Supabase project.

Building for Production

Generate a production build:

npm run build

This produces an optimized output in the build directory, configured for the Cloudflare Pages adapter. You can preview the production build locally:

npm run preview

Deploying to Cloudflare Pages

Deploy manually using Wrangler:

wrangler pages deploy .svelte-kit/cloudflare

Tip

For most workflows, deployments are handled automatically via CI/CD on push to main. Manual deployment with Wrangler is useful for testing preview builds or debugging deployment issues.

Set production environment variables through the Cloudflare dashboard or via Wrangler:

wrangler pages secret put SUPABASE_SERVICE_ROLE_KEY
wrangler pages secret put STRIPE_SECRET_KEY
wrangler pages secret put STRIPE_WEBHOOK_SECRET
wrangler pages secret put OPENAI_API_KEY
wrangler pages secret put ANTHROPIC_API_KEY
wrangler pages secret put CRON_SECRET

Each command prompts for the secret value interactively. Public variables (prefixed with PUBLIC_) should be set as plaintext environment variables in the Cloudflare Pages project settings.