Open BorisNen opened 2 years ago
Such settings are stored in browser's Local Storage
, for example
DIRIGIBLE.database
DIRIGIBLE.branding
DIRIGIBLE.IDE.GL.state.git
DIRIGIBLE.IDE.GL.state.terminal
DIRIGIBLE.IDE.GL.state.workbench
Proposal: Introduce new environment variable _(e.g. DIRIGIBLE_BRANDING_KEY
)_ to the list of branding related environment variables, that will be used as prefix when storing settings in the Local Storage
:
DIRIGIBLE_BRANDING_KEY=XXX
DIRIGIBLE.database
-> XXX.database
DIRIGIBLE.branding
-> XXX.branding
DIRIGIBLE.IDE.GL.state.git
-> XXX.IDE.GL.state.git
DIRIGIBLE.IDE.GL.state.terminal
-> XXX.IDE.GL.state.terminal
DIRIGIBLE.IDE.GL.state.workbench
-> XXX.IDE.GL.state.workbench
From xsk created by StanZGenchev: SAP/xsk#415
Describe the bug Currently, XSK and Dirigible share the same settings if running under the same domain. This can cause serious issues if the XSK and Dirigible versions mismatch.
Example scenario: XSK (built with Dirigible v5) and Dirigible v6 are used under the 'sap.com' domain for thing A and thing B, respectively. User X has to work with thing A and thing B, and uses the same PC to do so. Since XSK uses Dirigible v5 which has incompatible settings with Dirigible v6, there will most likely be visual glithes, usability bugs and/or pages not rendering correctly.
This is related to Dirigible issue #1071 - https://github.com/eclipse/dirigible/issues/1071