Environments
Hosts used in playbooks. Change the host per env; paths stay the same.
| Layer | Test / dev (playbook URLs) | Staging | Live |
|---|---|---|---|
| Core Backend API | https://backend-test.nellalink.com/public/api/v1/nellalink | https://backend-staging.nellalink.com/public/api/v1/nellalink | https://backend.nellalink.com/public/api/v1/nellalink |
| Core explorer | backend-test docs | staging /public/docs/api | live /public/docs/api |
| Middleware Backend | https://middleware-dev.nellalink.com | https://middleware-staging.nellalink.com | https://middleware.nellalink.com |
| Middleware explorer | middleware-dev docs | staging /docs/api | live /docs/api |
| User App | https://app-dev.nellalink.com | https://app-staging.nellalink.com | https://app.nellalink.com |
| Front-facing | https://business-dev.nellalink.com | https://business-staging.nellalink.com | https://business.nellalink.com |
User App GitHub Actions also set VITE_FRONT_FACING_URL to the matching business*.nellalink.com. On Front-facing faruq, guest routes (under basename /app/) are /:base/menu/:slug, /:base/cart/:slug, /:base/contact/:slug, /:base/orders/:slug, /:base/order-confirmation/:slug, and /print.
There is also backend-dev.nellalink.com in some Core deploy workflows. Playbooks use backend-test because that is the explorer you named for this portal.
Which ENV names activate a screen: Project Management activation. Source files: ENV / Metadata Catalog.