DZRZVD 杜戛地

A refreshed website for DZRZVD, a Taipei outdoor and functional apparel brand.

Pages

• Home and product collections
• Brand story
• Taipei retail location
• Dedicated Shopee catalog overview at /products
• Separate Shopee marketplace category pages at /products/[categorySlug]
• Protected operator interface at /admin/shopee-catalog

Development

npm install
npm run dev

Create a production build with:

npm run build

Vercel + Supabase catalog

The catalog implementation uses:

• Vercel Functions and a protected daily Cron route
• A separate protected daily Supabase database health check
• Supabase Postgres through its transaction pooler
• Supabase Auth for the invite-only operator interface
• Shopee Open Platform Shop, Product, and Public APIs

Copy .env.example to .env.local and configure the values locally. Never commit .env.local or any production credential.

Apply supabase/migrations to an isolated non-production Supabase project before connecting a production project. Add the invited operator's Supabase Auth UUID to app_private.app_admin.

For a linked Supabase project, use npm run db:push. For the local Supabase stack, use npm run db:reset. The SQL files under supabase/migrations are the only migration history; Drizzle schema definitions mirror them for application types and queries.

The application intentionally renders a setup state at /products when Supabase has not been configured, so builds and existing public pages remain available before platform provisioning is complete.

Vercel calls /api/cron/supabase-health daily at 06:17 UTC (14:17 Asia/Taipei), and /api/cron/shopee-sync daily at 18:00 UTC (02:00 Asia/Taipei). After Bearer authorization with CRON_SECRET, both routes write an atomic heartbeat to app_private.keepalive_heartbeat. The table is limited to one row per cron source and records the target Supabase project, last successful database write, and run count. The database and public Supabase URLs must resolve to the same project when both are configured. Set SUPABASE_PROJECT_REF to that project's ref so a consistently wrong set of URLs also fails before a heartbeat is written.

Apply the keepalive migration before deploying the route changes. After each automatic window, verify both rows are advancing with:

select source, project_ref, last_succeeded_at, run_count
from app_private.keepalive_heartbeat
order by source;

Run the full verification suite with:

npm test