Pivoted
Overview
Section titled “Overview”My LEF is LEF’s internal ERP, published under my.lef.digital.
This lane is PROD. Tier model: 3-tier (GUI → App → DB).
Components
Section titled “Components”GUI
- ERP:
https://my.lef.digital/ - Domain: lef.digital
- Reverse proxy: web.core.lef
Application tier
- Runtime: Runtime: Pivoted
- Backend upstream: confirm the upstream in the active NGINX config to find the environment VM and dependencies (on web.core.lef ).
Database tier
- Endpoint: pivoted.db.lef (via TCP proxy)
Operational notes
Section titled “Operational notes”- Dev lane: https://pivot.dev.lef/ (see Pivot).
- If the site is reachable but the app errors, check the reverse proxy upstream and then the backend service health.
Known risks / failure modes
Section titled “Known risks / failure modes”- DNS or certificate drift breaks access.
- Reverse proxy upstream drift sends traffic to the wrong backend.