Quickstart
Get PIPELINE up and running in under 10 minutes. This guide covers the essential setup to start tracking jobs immediately.For detailed installation instructions including database migrations and advanced configuration, see the Installation guide.
Prerequisites
Before starting, ensure you have:- Bun runtime installed (bun.sh)
- A Supabase account (supabase.com)
- Git for cloning the repository
PIPELINE uses Bun as the JavaScript runtime. If you prefer npm/yarn/pnpm, they should work but Bun is recommended for optimal performance.
Step 1: Clone the Repository
Step 2: Install Dependencies
Step 3: Set Up Supabase Project
Create a new Supabase project
- Go to supabase.com/dashboard
- Click New Project
- Choose a name (e.g., “pipeline-jobs”)
- Generate a secure database password
- Select a region close to you
- Click Create new project
Get your API credentials
Once your project is ready:
- Go to Settings → API
- Copy your Project URL
- Copy your anon public key
- Copy your service_role key (click “Reveal” first)
Step 4: Apply Database Migrations
PIPELINE includes 14 database migrations that set up tables, indexes, Row-Level Security policies, and triggers.- Using Supabase CLI (Recommended)
- Using Supabase Dashboard
Install the Supabase CLI if you haven’t already:Login and link your project:
Your project ref is the subdomain in your Supabase URL:
https://YOUR_PROJECT_REF.supabase.coStep 5: Start the Development Server
Step 6: Create Your Account
Sign up
- Open http://localhost:3000
- Click Sign Up
- Enter your email and password
- Click Create Account
Confirm your email
Check your inbox for a confirmation email from Supabase. Click the confirmation link.
For local development, you can skip email confirmation by enabling “Disable Email Confirmations” in Supabase Dashboard → Authentication → Settings.
Step 7: Track Your First Job
Congratulations! You’re now ready to track jobs.Add a job
Press
⌘N or click the Add Job button.Fill in the job details:- Title - Job title (e.g., “Senior Backend Engineer”)
- Company - Company name
- Location - Where the job is located
- URL - Link to the job posting
- Status - Current status (Saved, Applied, Interview, Offer, Rejected)
- Salary - Salary range (optional)
- Notes - Any additional notes
What’s Working Now
PIPELINE is under active development. Here’s what you can use today: ✅ Full authentication - Sign up, log in, password reset✅ Job tracking - Add, edit, delete jobs
✅ Kanban board - Drag-and-drop between statuses
✅ List view - Sort and filter jobs
✅ Job drawer - Detailed view with notes and timeline
✅ Command palette - Keyboard-first navigation
✅ Settings - Profile, account, preferences ⚠️ In Progress:
- Dashboard analytics (displays mock data)
- AI match scoring
- Job board scraping
- Discord notifications
- Export functionality
Next Steps
Installation Guide
Detailed setup including database schema, TypeScript types, and advanced configuration.
Configuration
Configure AI services, integrations, and feature flags.
Architecture
Understand how PIPELINE is built and organized.
API Reference
Explore the API endpoints and data models.
Troubleshooting
Port 3000 Already in Use
Supabase Connection Errors
Error: Invalid API key
Error: Invalid API key
Double-check your
.env.local file:- Ensure no extra spaces around the
=signs - Verify you copied the full API keys
- Make sure you’re using the anon key for
NEXT_PUBLIC_SUPABASE_ANON_KEY
Error: relation 'jobs' does not exist
Error: relation 'jobs' does not exist
This means database migrations weren’t applied. Go back to Step 4 and apply migrations using either the CLI or dashboard method.
Error: Row Level Security policy violation
Error: Row Level Security policy violation
This usually happens if:
- Migrations weren’t fully applied (missing RLS policies)
- You’re not properly authenticated
- Try logging out and back in
Development Server Won’t Start
Getting Help
If you encounter issues:- Check the Installation Guide for detailed setup
- Review Common Issues documentation
- Search GitHub Issues
- Join our Discord community
For production deployment, see the Deployment Guide for instructions on deploying to Vercel, Netlify, or self-hosted environments.