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
It is good practice to have any configuration done through environment variables.
With the current set-up a user can put domain model(s) into the "knowledgebases" folder and this folder will be mounted by the system-modeller and any domain models within will be loaded on boot.
It would be better (and clearer) if we also had the ability to download a specified domain model(s) automatically based on an environment variable defined in .env (or wherever).
The text was updated successfully, but these errors were encountered:
The solution we discussed is to create a custom entrypoint for the ssm container (as we have done for keycloak and nginx) so that the domain model(s) are downloaded first and then tomcat is started.
We could have a comma-separated list of domain model URLs in an environment variable.
It is good practice to have any configuration done through environment variables.
With the current set-up a user can put domain model(s) into the "knowledgebases" folder and this folder will be mounted by the system-modeller and any domain models within will be loaded on boot.
It would be better (and clearer) if we also had the ability to download a specified domain model(s) automatically based on an environment variable defined in
.env
(or wherever).The text was updated successfully, but these errors were encountered: