Core Backend playbook — how to build the source of truth
Job: store users and entities. How to configure the core backend for this PMS (including API-key path settings for IDOR). Rarely talk to the outside world.
BookDirect is a PMS on generic Smart Meta Manager. Conventions live in these playbooks — not as new hotel tables in Laravel. Laravel should be installed and running on server.
Playbooks
| Page | What it is |
|---|---|
| Recommended usage | Use this / do not add this |
| Auth | Register, login, refresh, logout |
| Entities | property, room, rate_plan, booking, payment |
| ENV / Metadata Catalog | property_category, amenities |
| Search indexes | Category, tags, metadata — Core narrow queries for Middleware |
Turn a feature on: Project Management.
Explorer: https://backend-dev.bookdirect.live/public/docs/api#/
Contract: specs/core/v1/openapi.yaml
One property type
Frontend creates properties via Middleware Backend (POST .../api/v1/nellalink/properties). Core still stores property. Metadata property_category = hotel | shortlet | apartment. Never nll_hotel / nll_shortlet / nll_apartment.
What Core Backend must not grow into
No Paystack, Resend, GuestTraction, or date-overlap availability engine. Those are Middleware Backend playbooks.