| Service | Default |
|---|---|
| Ibnu Sina frontend | http://localhost:3002 |
| Ibnu Sina backend | http://localhost:8082 |
| Utopia OE | http://localhost:8081 |
| Utopiaspace Ops web | http://localhost:3010 |
| API prefix | /api/v1 |
The backend runs through Docker Compose. The frontend uses Node.js 20+ and its committed lockfile. Use only a development database and development storage keys locally.
NEXT_PUBLIC_* values are exposed to the browser and must not contain secrets.| Group | Examples of ownership |
|---|---|
| Application | URLs, environment, key, version/commit, logging and timezone |
| Database | Supabase pooler host, credentials, SSL and prepare/persistence flags |
| Identity | Hub URL, JWT verification, policy key, profile resolver and cookie settings |
| Storage | Private/public disks, S3 endpoint, buckets and upload limits |
| OE/Ops | API token prefix, partner base URL/token and BU/unit registration |
| Fleet | Hub vehicle-listing endpoint/secret and sync policy |
| Messaging | Mail provider, sender and notification delivery settings |
| Legacy | Ingestion endpoints/secrets, projection schedule and observability |
| Frontend | Public API URL, Hub cookie source, app identity and build version |
Store secret values in the deployment platform’s secret manager. Documentation should record variable names and owners, not credentials.
The operational schema is plain SQL under backend/supabase/migrations. Apply migrations in filename order through the approved Supabase process. Review data migrations as carefully as schema changes because many files seed status vocabularies, permissions, product prefixes and legacy mappings.
Never reset a linked production database. For a correction, add a forward migration that preserves existing records and auditability.
The committed workflow deploys the frontend to Vercel when frontend changes reach main. development is the shared integration branch, and an automated release PR keeps development → main visible for a human merge decision.
The Vercel workflow:
Backend-only releases do not trigger the frontend path filter.
The repository contains a production Docker image and Laravel runtime configuration, but no equivalent committed backend deployment workflow was identified. Before changing production, confirm the actual platform, application identifier, deployment trigger, migration procedure and rollback owner.
Code expecting a new table or column must not go live before the compatible migration. Destructive changes require a staged release where both old and new shapes are temporarily supported.
After a release, verify the exact deployed commit/version, API health, sign-in, branch scope and the business areas affected by the change. For state-machine or integration work, verify both the local record and its downstream queue/outbox result. A green frontend deployment does not prove database migration, backend deployment, OE routing or AutoCount delivery.
Frontend, backend and database are separate rollback concerns. Reverting only one can leave incompatible contracts. Database migrations are forward-only: repair with a new migration. Preserve integration idempotency keys and never replay money or stock writes blindly during recovery.