This should map to con environmental variable that is set in the container and can be dynamically assigned during runtime of a Simphony-Remote session.
It is expected that an “admin” user will assign the configurable to the image when registering the application. The value of the configurable should be exposed in the backend (maybe with a default value of 0), but does not need to be set in the frontend by the user (like the window size).
This needs to be well documented as its a sub-optimal approach - the image source code itself should really register the additional configurable object. Additionally, the "configurables" framework seems complex, so we may need some exploratory time here.
This should map to con environmental variable that is set in the container and can be dynamically assigned during runtime of a Simphony-Remote session.
It is expected that an “admin” user will assign the configurable to the image when registering the application. The value of the configurable should be exposed in the backend (maybe with a default value of 0), but does not need to be set in the frontend by the user (like the window size).
This needs to be well documented as its a sub-optimal approach - the image source code itself should really register the additional configurable object. Additionally, the "configurables" framework seems complex, so we may need some exploratory time here.