Licensing
Most of Bragi is available to every client. A small number of features are licensed, and stay off until a licence covering them is entered on the Settings page.
Bragi runs perfectly well with no licence at all. An unlicensed system simply behaves as it always has, with every licensed feature off.
Entering a licence
Cortex issues a licence as a single key: a long line of letters, numbers, dashes and underscores. Paste it into the Licence field on Admin > Settings and save.
Saving tells you if the key cannot be read, which usually means it was pasted short - copy the whole key and save again. If it still will not read, contact Cortex. Otherwise the features your licence covers appear immediately.
The key is safe to paste from an email. Line breaks and stray spaces picked up in transit are ignored, so it does not matter if it arrives wrapped across several lines.
A licence covers the whole system, not one Environment, so it is entered once wherever you happen to be.
Licensed features
Feature | What it covers |
|---|---|
Multiple Develop Environments | Holding more than one |
What happens without a licence
A licensed feature that has not been paid for is not quietly ignored - Bragi stops the work it covers and says so.
For multiple Develop Environments, the chain rooted at the Primary Develop Environment is the one every system is entitled to. Any other chain is held without a licence, and while that is the case:
Every Environment in it is read only. No Config can be saved there.
Nothing can be deployed into it, restored into it, or imported into it.
Its Scheduler does not run, so no Job in that chain starts.
A banner appears on every page naming the Environments affected.
Nothing is deleted and no configuration is lost. The chain stays visible so it can be tidied up, and entering a licence that covers it starts everything running again on the next page load - there is nothing to rebuild and no restart needed.
If the chain was added by mistake, remove its Environments on the Environments page and the banner clears.
Renewing and expiry
A licence may carry an expiry date, or none at all. An expired licence still reads - Bragi tells you it has run out rather than that it is unrecognised - but it grants nothing. Replacing the key with a renewed one turns the features back on as soon as it is saved.
Letting a licence lapse never takes work away. Multiple Develop Environments, for instance, gates adding a chain: a system that already holds several keeps them, and keeps the screens for managing them, whatever the licence says.