You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The UX around installing Flagsmith on-prem can be improved with some additional license management. Suggested approach:
Flagsmith generates an encrypted file with its private key that includes meta data such as customer name, department name, number of seats, expiry date and possibly other data
This file is then sent to the customer
When starting the EE version of Flagsmith, this file can be passed in with different methods (ENV var, attached volume etc) so that the file can be read
The file is decrypted with the Flagsmith public key and the meta data used to help configure the service
We should also display the org name and department name in the header of the dashboard.
The text was updated successfully, but these errors were encountered:
The UX around installing Flagsmith on-prem can be improved with some additional license management. Suggested approach:
We should also display the org name and department name in the header of the dashboard.
The text was updated successfully, but these errors were encountered: