Open Boat Fishing — Booking Platform

Multi-tenant ticketing and check-in platform for party fishing boat operators. Each operator gets their own isolated deployment (Vercel + Neon Postgres) from this shared codebase.

---

What's in the box

App	Description
apps/web	Next.js 14 — marketing site, booking calendar, checkout, boarding passes, admin dashboard, API routes
apps/mobile	Expo SDK 53 — consumer booking app (trips calendar, Stripe Payment Sheet, offline tickets wallet, Account tab with OTP sign-in) + mate check-in app (same codebase, separate EAS profile)
packages/db	Drizzle ORM schema + migrations (shared source of truth)

The mate check-in app (QR scanner, offline manifest, PIN auth) is built from the same apps/mobile codebase using the mate EAS build profile (EXPO_PUBLIC_APP_VARIANT=mate).

---

Prerequisites

• Node.js 20+
• pnpm 9+ (npm install -g pnpm)
• Expo CLI (npm install -g expo-cli)
• EAS CLI (npm install -g eas-cli) — for mobile device builds
• Stripe CLI (brew install stripe/stripe-cli/stripe) — for local webhook forwarding
• A Neon Postgres database (free tier works for dev)
• A Stripe account with Connect enabled (platform account)
• A Resend account for transactional email
• An Apple Developer account ($99/yr) — required for iOS device builds and App Store

---

Monorepo setup

git clone <repo>
cd open-boat-fishing
pnpm install

---

Setting up a new operator

1. Database

Create a Neon project. Copy the connection string.

# In packages/db — run migrations against the new database
DATABASE_URL="postgres://..." pnpm db:migrate

Then seed development data (creates one operator row, 4 vessels, products, prices, and ~150 trips):

DATABASE_URL="postgres://..." pnpm --filter @openboat/db seed

For production, replace the seed script with real operator data or use the admin dashboard.

2. Stripe

• Create or log in to your Stripe platform account.
• In Connect settings, enable Destination Charges.
• The operator needs their own Stripe account. Onboard them via Stripe Connect (or create a test connected account in the dashboard).
• Note the connected account ID (acct_...).

3. Web app environment variables

Create apps/web/.env.local:

# Database
DATABASE_URL=postgres://...

# Stripe (platform account)
STRIPE_SECRET_KEY=sk_test_...
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_test_...
STRIPE_WEBHOOK_SECRET=whsec_...        # from `stripe listen` in dev; from Stripe dashboard in prod
STRIPE_CONNECTED_ACCOUNT_ID=acct_...  # operator's connected account

# App
NEXT_PUBLIC_APP_URL=https://yourclient.com   # used in boarding pass links in emails

# Email (Resend)
RESEND_API_KEY=re_...

# Auth (signs mate + customer tokens)
SESSION_SECRET=<32+ char random hex>   # generate with: openssl rand -hex 32

# Vercel cron auth (required for push notification reminders)
CRON_SECRET=<32+ char random hex>      # must also be set in Vercel dashboard

4. Mobile app environment variables

Create apps/mobile/.env.local for local dev:

EXPO_PUBLIC_API_URL=http://localhost:3000

EXPO_PUBLIC_STRIPE_PUBLISHABLE_KEY=pk_test_...

# Apple Pay / Google Pay
EXPO_PUBLIC_APPLE_MERCHANT_ID=merchant.com.yourclient.app
EXPO_PUBLIC_URL_SCHEME=yourclientapp
EXPO_PUBLIC_MERCHANT_NAME=Your Client Name

# Set to "mate" to run the mate check-in app instead of the consumer app
# EXPO_PUBLIC_APP_VARIANT=mate

For EAS builds, set these in apps/mobile/eas.json under the appropriate build profile (see Mobile builds below).

5. app.json — per-operator mobile identity

Edit apps/mobile/app.json to match the operator:

{
  "expo": {
    "name": "Your Operator Name",
    "slug": "your-operator-slug",
    "scheme": "youroperatorapp",
    "ios": {
      "bundleIdentifier": "com.youroperator.fishing"
    },
    "android": {
      "package": "com.youroperator.fishing"
    }
  }
}

Each operator needs a unique bundle ID and scheme. For a second operator, either fork the repo or use EAS build profiles to override these values.

---

Local development

# Start everything (Turborepo — web + mobile Metro in parallel)
pnpm dev

# Or individually:
pnpm --filter @openboat/web dev        # Next.js on :3001 (or :3000)
pnpm --filter @openboat/mobile dev -- --clear   # Expo Metro on :8081

# Forward Stripe webhooks to local server (required for booking confirmation + wallet sync)
stripe listen --forward-to localhost:3001/api/webhooks/stripe

Webhook note: booking status only transitions to confirmed (and tickets appear in the mobile wallet) after payment_intent.succeeded fires. In local dev this requires stripe listen running.

Running in the iOS simulator

pnpm --filter @openboat/mobile ios

The app opens automatically. Use test card 4242 4242 4242 4242 with any future expiry and any CVC.

Running on a physical iOS device

Requires an EAS development build — see Mobile builds. The simulator build won't install on a device.

---

Database commands

# Run migrations
DATABASE_URL="..." pnpm db:migrate

# Generate migration from schema changes
pnpm --filter @openboat/db generate

# Open Drizzle Studio (visual DB browser)
DATABASE_URL="..." pnpm db:studio

---

This is the beginning of the README. Read the rest at the original. Read the full README ↗