Property Management setup

Configuration detected

1. Environment

Copy .env.example to .env.local and fill in the values below. Both the new sb_publishable_… / sb_secret_… keys and the legacy anon / service_role pair are accepted.

NEXT_PUBLIC_SUPABASE_URLProject URL from Supabase → Project Settings → API
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEYPublishable key (or the legacy NEXT_PUBLIC_SUPABASE_ANON_KEY)
SUPABASE_SECRET_KEYOr the legacy SUPABASE_SERVICE_ROLE_KEY. Needed only for scheduled jobs

2. Database

Apply the migrations in order against your Supabase project's SQL editor, or with the Supabase CLI:

supabase db push

No CLI? Paste supabase/ALL_MIGRATIONS.sql into the SQL Editor — it is every migration concatenated, and applies in one run. Do not run supabase/local/00_shim.sql against a real project: those objects already exist there.

3. First user

Create a user in Supabase → Authentication → Users, then set their role:

update profiles set role = 'super_admin'
where email = 'you@drp.ae';