ENV / Metadata Catalog

Project Management (PM) lookup across every playbook. Names only — never paste secret values.

Each playbook has the same page for its own slice:

Playbook	Catalog
Frontend	ENV / Metadata Catalog
Frontend — Marketplace	ENV / Metadata Catalog
Frontend — Extranet	ENV / Metadata Catalog
Middleware Backend	ENV / Metadata Catalog
Core Backend	ENV / Metadata Catalog (canonical `meta_key` list)

Screen or function → status, winner, ENVs: activation matrix. Terms: glossary.

How to use

Find the flow on the activation matrix.
Open that playbook’s ENV / Metadata Catalog and set only the names listed there.
Confirm Core keys on the Core catalog before adding a new extra_data / meta_key field.

Name	Layer	Turns on
`NEXT_PUBLIC_API_BASE_URL`	Frontend	Core Backend origin
`NEXT_PUBLIC_MIDDLEWARE_API_URL`	Frontend	Middleware Backend origin
`NEXT_PUBLIC_API_KEY`	Frontend	Public browse / auth key in the browser
`NEXT_PUBLIC_PARTNER_SESSION_COOKIE_NAME`	Frontend — Extranet	Partner session cookie
`NEXT_PUBLIC_DIRECT_S3_UPLOAD`	Frontend	`true` = browser PUT to S3
`VITE_*` (legacy inject)	Frontend	Next reads `NEXT_PUBLIC_*` first
`NELLALINK_USER_JWT_SECRET_KEY`	Middleware Backend	Verify Core JWT (`iss` nellalink)
`ROUTE_FILE_MANAGER_BACKEND_BASEURL`	Middleware Backend	Core API base used by live folders
`ROUTE_FILE_MANAGER_X_API_KEY_CORE_BACKEND`	Middleware Backend	Server-only Core key
`PAYSTACK_SECRET_KEY`	Middleware Backend	Payments initialize + webhook HMAC
`ROUTE_FILE_MANAGER_AWS_*`	Middleware Backend	S3 presign
Core JWT secret (`NELLALINK_JWT_SECRET` in Laravel config / `ENV-SAMPLE`)	Core Backend	Sign / verify user JWT — Frontend never holds this

Canonical lodging meta_key list: Core Backend ENV / Metadata Catalog.

Frontend: frontend-bookdirect-user-app/.github/workflows/deploy-develop.yml
Middleware: .env-sample plus src/routes/{properties,rates-packages,bookings,availability,payments,reservations,file-manager}/.env-sample
Core: ENV-SAMPLE if present, else config/nellalink-laravel.php