LogoDirFast
  • Features
  • Compare
  • Pricing
  • Free Tools
  • Docs
  • Demo
LogoDirFast

Start here

IntroductionQuickstart

Configure

SupabaseEnvironment variablesCustomization

Deploy

Deploy to Vercel
DirFast Docs

DirFast Docs

Deploy to Vercel

Deploy DirFast, connect Supabase, and verify production integrations.

PreviousCustomization

On this page

LogoDirFast

A production-ready directory template for shipping your idea.

Product
  • Features
  • Compare
  • Pricing
Resources
  • Free Tools
  • Logo generator
  • OG image generator
  • Documentation
  • Live demo
Compare
  • Mkdirs
  • Dirstarter
Company
  • About
  • Privacy Policy
  • Terms of Service
  • Refund Policy
  • Sitemap
Copyright © 2026 All Rights Reserved.

Vercel can deploy DirFast directly from the Git repository. Complete the local setup first so the production deployment uses a known-good schema and configuration.

Prepare Supabase production

Create or select a hosted Supabase project, then push the repository migrations.

supabase login
supabase link --project-ref <project-ref>
supabase db push

Copy the project's URL, anon key, and service role key from Project Settings → API. Follow the Supabase guide to configure the Auth Site URL, callback URL, storage bucket, and first admin user.

Import the repository

  1. Open the Vercel dashboard and select Add New → Project.
  2. Import the Git repository containing your DirFast source.
  3. Keep the detected Next.js framework and the repository's Yarn install and build commands.
  4. Select the production branch and create the project.

Add environment variables

Add the required values under Project Settings → Environment Variables for Production, Preview, and Development as needed.

NEXT_PUBLIC_APP_URL=https://<your-domain>
NEXT_PUBLIC_SUPABASE_URL=https://<project-ref>.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=<supabase-anon-key>
SUPABASE_SERVICE_ROLE_KEY=<supabase-service-role-key>

Add the Resend, Dodo Payments, Inngest, AI, analytics, and notification variables described in Environment variables. Use test-mode payment credentials for Preview and live credentials for Production.

Deploy

Click Deploy and watch the build logs. A successful build should finish with the Next.js production output. Open the generated deployment URL and verify the home page, a listing page, authentication, and /admin.

Set NEXT_PUBLIC_APP_URL to the final production domain after connecting it in Vercel, then redeploy. This value is used for canonical metadata, Auth callback links, email links, and the sitemap.

Connect production callbacks

In Supabase Authentication, set the Site URL to the production domain and add:

https://<your-domain>/auth/callback

In Dodo Payments, set the webhook URL to:

https://<your-domain>/api/webhook

If Inngest is enabled, register:

https://<your-domain>/api/inngest

Use the exact production URLs and signing keys supplied by each provider.

Production checklist

  • The production Supabase migrations are applied.
  • NEXT_PUBLIC_APP_URL matches the Vercel custom domain.
  • Supabase Auth redirects to /auth/callback on that domain.
  • The first admin profile has the ADMIN role and /admin is accessible.
  • Resend has a verified sending domain.
  • Dodo product IDs, environment, and webhook key match the account being used.
  • AI and analytics variables are present when those features are enabled.
  • The sitemap is available at /sitemap.xml and robots metadata points to it.

When you change environment variables in Vercel, redeploy the project so the new values are used by the build and server functions.