Environment boundaries, release verification and rollback precautions for Encik Beku.
| Concern | Development | Production |
|---|---|---|
| Frontend | Next.js development server or Vercel environment | Vercel production deployment |
| Backend | Docker container on port 8080 | DigitalOcean App Platform container with Nginx and PHP-FPM |
| Database | Encik Beku development Supabase project | Encik Beku production Supabase project |
| Identity | Shared UtopiaSpace Supabase identity | Shared UtopiaSpace Supabase identity |
| Queue | Synchronous | Synchronous in the inspected configuration |
| Scheduler | Manual/external unless separately configured | Must be verified; the application container alone does not prove it runs |
The exact project IDs, service IDs, domains, dashboard owners and billing owners must be recorded in the team's approved operational records during the live handover. They should not be guessed from source code.
The inspected source repository explicitly warns that pushing development can deploy both applications:
.github/workflows/frontend-development.yaml builds and deploys the frontend to Vercel's production URL.The workflow strips Git metadata before the Vercel build and injects the GitHub SHA as VERCEL_GIT_COMMIT_SHA. The frontend version uses the workflow run number. The backend exposes build identity from APP_VERSION and APP_COMMIT.
After deployment, record evidence for all applicable checks:
/api/v1/health is healthy./api/v1/version reports the intended build.Configuration is distributed across:
The repository does not contain a complete backend .env.example. This is an active handover gap. The incoming owner must receive a key-name inventory and owner, never secret values in this wiki.
Minimum frontend keys documented in source:
| Key | Purpose |
|---|---|
NEXT_PUBLIC_BACKEND_URL |
Browser-visible backend base URL |
BACKEND_INTERNAL_URL |
Server-side/internal backend URL |
NEXT_PUBLIC_SUPABASE_URL |
Shared UtopiaSpace Supabase URL used by the frontend |
Critical backend key groups include application identity, PostgreSQL connection, shared Supabase auth, cookie/domain policy, Utopia policy/profile endpoints, upload storage, OE integration, vehicle-listing secret, rate limits and logging. Ownership remains unverified until a sanitized backend example and responsible owner are recorded.
The authoritative schema is backend/supabase/migrations. Laravel migrations are not used for this application schema.
cd backend
supabase link --project-ref <verified-project-ref>
supabase db push
Before running this against any environment, verify the linked project explicitly. Migration filenames must have a unique, strictly increasing timestamp later than the newest existing migration.