window.__CABINE_CONFIG__ before Cabine starts. One installation serves one institution.
How Cabine reads a key
Cabine resolves each key in this order:- The value in
window.__CABINE_CONFIG__, when the key is there and valid. - The value set when the Cabine bundle was built, when
window.__CABINE_CONFIG__does not carry the key. - Unset.
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. It also hides the workspace of that rail in the workspace switcher, the sidebar and the command palette. A saved link to a screen of that rail shows a view that names the missing key, and Cabine makes no call to the rail. The Cabine and Administração workspaces always show. The SPI workspace depends onVITE_SPI_URL alone.
The browser calls each rail at its address. Each rail must allow the origin where operators open Cabine.
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.

