To deploy your Zoco Collective site to Hostinger, you have a few options:

Option 1: Deploy to Vercel (Recommended - Easiest)

Since your site is built with Next.js, Vercel is the ideal host:

1. Click the "Publish" button in the top right of v0
2. This will automatically deploy your site to Vercel for free
3. You can then point your Hostinger domain to Vercel's nameservers

Option 2: Deploy to Hostinger Directly

Hostinger does support Node.js apps, but it requires more manual setup:

1. Download the project:

   • Click the three dots (⋯) in the top right of your v0 block
   • Select "Download ZIP"

2. Prepare your project:

   • Extract the ZIP
   • Run npm install locally to install dependencies
   • Run npm run build to create an optimized build

3. Upload to Hostinger:

   • Use Hostinger's file manager or SFTP to upload your project files

   • Hostinger's Node.js hosting will need:

     • The .next folder (your build)
     • package.json and package-lock.json
     • public folder
     • node_modules (or Hostinger will install from package.json)

4. Configure on Hostinger:

   • Set the start command to: npm run start
   • Set the port (usually 3000, but check Hostinger's docs)
   • Ensure Node.js 18+ is enabled

Option 3: Use GitHub + Hostinger's Git Integration

1. Push your project to GitHub
2. Connect Hostinger to your GitHub repo for auto-deployment

I'd recommend Option 1 (Vercel) — it's designed for Next.js and handles everything automatically. Would you like me to help with any of these steps?

I see the issue. The API routes are trying to connect to Supabase, but the environment variables aren't set on Hostinger. You have two options:

Option A: Set Supabase Environment Variables on Hostinger (Recommended)

1. Log into your Hostinger control panel
2. Go to Website → Node.js Environment Variables (or similar)

3. Add these two variables:

   • NEXT_PUBLIC_SUPABASE_URL — Your Supabase project URL
   • SUPABASE_SERVICE_ROLE_KEY — Your Supabase service role key
4. Re-deploy your project

Get these from your Supabase project settings → Project Settings → API.

Option B: Disable Supabase (If You're Not Using It)

If you're not using the gallery submissions feature, I can remove these API routes so the build doesn't fail. Which would you prefer?