Local Environment Setup

Follow these steps to configure your local Envault environment.

1. Supabase Local Stack

The database, edge functions, and authentication are managed by Supabase.

# Start Docker Desktop first, then run:
supabase start

This commands spin up the local Postgres instance, GoTrue (auth), Storage, and Realtime services. You will see API URLs and the local service keys provided in your terminal output.

2. Next.js Web App

Copy the local environment variables template:

cp .env.example .env.local

Update .env.local with the values provided by supabase start (e.g., NEXT_PUBLIC_SUPABASE_URL and NEXT_PUBLIC_SUPABASE_ANON_KEY).

Run the development server:

npm install

npm run dev

The web dashboard will be accessible at http://localhost:3000.

3. Go CLI Development

To test the Go CLI locally during development:

Navigate to the Go CLI directory:

cd cli-go

Download the requisite Go modules:

go mod download

Build the local executable binary:

go build -o envault main.go

Run your local binary against your Next.js and Supabase backend:

./envault login

Make sure the CLI is pointing to http://localhost:3000 rather than the production endpoint. There are typically build flags or environment variables (e.g., ENVAULT_API_URL=http://localhost:3000) used for overriding the cloud destination.