Supabase Cheat Sheet

Supabase cheat sheet with real commands and snippets for setup, core workflows, debugging, and production-safe automation patterns. If you are working across tools, pair this with the gcloud Cheat Sheet and Prisma Cheat Sheet.

Setup and Installation

Goal: Verify installation and CLI metadata

# Resolve command path from current shell
command -v supabase

# Print installed version to confirm runtime
supabase --version

# Read top-level help before using subcommands
supabase --help

Goal: Install or upgrade the tool on a workstation

# Install Supabase CLI from official Homebrew tap
brew install supabase/tap/supabase

# Verify Supabase CLI installation
supabase --version

Goal: Run day-to-day commands

# Authenticate Supabase CLI
supabase login

# Initialize Supabase project files
supabase init

# Start local Supabase stack
supabase start

# Apply local migrations to remote database
supabase db push

Core Workflows

Goal: Capture command help for quick offline lookup

# Create docs folder for generated command references
mkdir -p docs/cli

# Write help output to a timestamped file
supabase --help > docs/cli/supabase-help.txt

# Search help output for a keyword
rg "config|auth|deploy" docs/cli/supabase-help.txt

Goal: Wrap repetitive commands in a script

# Create scripts directory for local automation
mkdir -p scripts

# Write repeatable health-check script
cat > scripts/check-supabase.sh <<'SH'
#!/usr/bin/env bash
set -euo pipefail
supabase --version
supabase --help >/dev/null
SH

# Make script executable and run it
chmod +x scripts/check-supabase.sh && ./scripts/check-supabase.sh

Configuration and Environment

Goal: Pin environment variables for predictable runs

# Define environment profile for local commands
export SUPABASE_PROFILE=dev

# Persist profile in local shell configuration
echo 'export SUPABASE_PROFILE=dev' >> ~/.zshrc

# Reload shell profile changes
source ~/.zshrc

Automation and CI

Goal: Add tool checks to CI pipeline

# Run lint/test/build in strict mode
set -euo pipefail

# Verify CLI exists before invoking workflow
command -v supabase

# Exit quickly if command is unavailable
supabase --version

Debugging and Troubleshooting

Goal: Collect diagnostics when commands fail

# Capture command output and exit code
supabase --help > /tmp/supabase-debug.log 2>&1; echo $?

# Inspect captured diagnostics
tail -n 80 /tmp/supabase-debug.log

# Check current shell PATH entries
echo $PATH | tr ':' '\n'

Common Gotchas

• Pin Supabase versions in CI so local and pipeline behavior match.
• Check tool authentication context before running write or deploy commands.
• Prefer non-interactive flags in scripts to avoid stalled jobs.
• Capture stderr logs in CI artifacts for faster incident triage.
• Keep secrets in environment variables, not committed scripts.

Related Sheets

• gcloud Cheat Sheet — daily gcloud commands and production-ready examples.
• Prisma Cheat Sheet — daily Prisma commands and production-ready examples.
• VS Code Cheat Sheet — daily VS Code commands and production-ready examples.