1. Create a new application in Clerk Dashboard
2. Copy your API keys from the dashboard
3. Paste them into your .env.local file:

   NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY=your_clerk_publishable_key
   CLERK_SECRET_KEY=your_clerk_secret_key
   

Note: All Clerk integration code is already implemented in the project.

1. Create a new project in Supabase Dashboard
2. Copy your project URL and anon key from Project Settings > API
3. Paste them into your .env.local file:

   NEXT_PUBLIC_SUPABASE_URL=your_supabase_project_url
   NEXT_PUBLIC_SUPABASE_ANON_KEY=your_supabase_anon_key
   SUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key
   

4. Set up your database schema by simply copying the contents of schema_export.sql and pasting it into the SQL Editor in your Supabase dashboard

Note: All Supabase integration code is already implemented in the project.

This important step ensures your Clerk authentication seamlessly integrates with your Supabase database:

1. Visit Clerk's Supabase Setup Page
2. Select your Clerk application
3. Copy the URL provided by Clerk

In your Supabase dashboard:

1. Go to Project Settings → Authentication → Third Party Authentication
2. Click "Add Provider" and select "Clerk"
3. Paste the connection URL you copied from Clerk
4. Save the configuration

Now your Clerk users will automatically sync with Supabase, allowing you to use row-level security with the authenticated user's ID.

Note: This integration allows you to use Supabase's powerful row-level security while leveraging Clerk's superior authentication experience.

1. Create an account on Polar.sh
2. Generate your access token and webhook secret from the dashboard
3. Paste them into your .env.local file:

   POLAR_ACCESS_TOKEN=your_polar_access_token
   POLAR_WEBHOOK_SECRET=your_webhook_secret_from_polar
   

Note: All Polar.sh integration code is already implemented in the project.

Setting up the Customer Portal:

The Polar Customer Portal allows users to manage their subscriptions. This boilerplate includes a "Manage Subscription" button on the billing page that redirects users to the Polar Customer Portal.

1. The portal is configured at /app/portal/route.ts using the CustomerPortal from @polar-sh/nextjs.
2. Make sure your POLAR_ACCESS_TOKEN is set in your .env.local file.
3. The portal uses the user's email as the customer ID by default. Modify the getCustomerId function if you need a different identifier.

Setting up Webhooks for Local Development:

During development, you need a public URL to receive webhook events from Polar. Here's how to set it up:

1. Install ngrok if you haven't already
2. Start your Next.js application:

   npm run dev

3. In a new terminal window, create a tunnel to your local server:

   ngrok http 3000

4. Copy the HTTPS URL provided by ngrok (e.g., https://a1b2-103-199-202-181.ngrok-free.app)
5. In the Polar dashboard, set your webhook URL by appending the API path:

   https://your-ngrok-url.ngrok-free.app/api/webhook/polar
   

6. Polar will generate a WEBHOOK_SECRET for you
7. Update your .env.local file with this new secret:

   POLAR_WEBHOOK_SECRET=your_new_webhook_secret
   

Now Polar can send real-time payment events to your local development environment!

1. Connect your GitHub repository to Railway
2. Set environment variables
3. Deploy with:

   npm run build && npm start

1. Build your Docker image:

   docker build -t my-getshipkit-app .

2. Run your container:

   docker run -p 3000:3000 --env-file .env.production my-getshipkit-app

• Issue: Users can't log in

  • Verify Clerk API keys are correct in your .env file
  • Check that redirect URLs match exactly in both Clerk dashboard and your code
  • Look for CORS issues in browser console

• Issue: Social logins not working

  • Ensure social providers are properly configured in Clerk dashboard
  • Check callback URLs are correctly set

• Issue: "Error connecting to database"

  • Verify Supabase URL and keys are correct
  • Check if your IP is allowed in Supabase dashboard
  • Make sure your database schema matches the expected structure

• Issue: Missing tables or columns

  • Ensure you've pasted the full contents of schema_export.sql into Supabase SQL Editor
  • Run the SQL commands in the Supabase dashboard

• Issue: Payments not processing

  • Verify Polar.sh credentials
  • Check webhook endpoints are correctly configured
  • Test with Polar.sh's sandbox mode first

• Issue: Webhooks not being received

  • Use a tool like ngrok to expose local endpoints for testing
  • Check webhook secret is correctly set