Skip to main content
Lerian Cabine reads its service addresses and institution settings at run time. The deployment serves a script that sets window.__CABINE_CONFIG__ before Cabine starts. One installation serves one institution.

How Cabine reads a key

Cabine resolves each key in this order:
  1. The value in window.__CABINE_CONFIG__, when the key is there and valid.
  2. The value set when the Cabine bundle was built, when window.__CABINE_CONFIG__ does not carry the key.
  3. Unset.
An empty string is valid. It unsets the key, and it hides the build value. A value that is not valid is treated as unset. It also hides the build value, so a typo cannot fall back to an address from another environment. Cabine trims a run-time value. Cabine reads only its allowed run-time keys and ignores the rest.

Access Manager and Cabine API addresses

Cabine adds the route path to each address.

Rail addresses

Without the address of a rail, Cabine cannot call that rail.

Readiness addresses

Cabine reads the readiness of a rail at /readyz on the readiness address. Cabine leaves out a rail that has no address. When a readiness key is unset, Cabine uses the address in the last column.

Institution

Floors

Floors that an operator sets are saved in that browser only. They override the deployment default in that browser. An operator sets the floors on the Configuração page of the STR and SPI workspaces, in the fields Piso da reserva and Limiar da Conta PI, and saves with Salvar. Each field accepts up to two decimal places. Clearing a field returns to the deployment default. Without a default, the alert stops.