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
{{ message }}
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.
In function build_config the configuration file is created as one big config element.
If might be handy to separate out the different parts in separate function so those separate functions can be override in app_specific.
So create a separate function that only handles unit-test specific replacements, and one specific for the triggers db and so on.
One use-case is when you have a D-node/E-node config where all your data is on the D-nodes and all your http-servers are on the E-nodes and you want to enable the unittest section. You want to override the assignment and forest-data-directory.
These override statements can be done in an override function in the app_specific.rb file
The text was updated successfully, but these errors were encountered:
In a nutshell: you cannot control server, db, and forest creation for generated parts of ml-config, like schemas, triggers, test, rest. You could add properties to allow influencing them from properties files, but overriding function from app_specific might be an elegant approach as well.
In function build_config the configuration file is created as one big config element.
If might be handy to separate out the different parts in separate function so those separate functions can be override in app_specific.
So create a separate function that only handles unit-test specific replacements, and one specific for the triggers db and so on.
One use-case is when you have a D-node/E-node config where all your data is on the D-nodes and all your http-servers are on the E-nodes and you want to enable the unittest section. You want to override the assignment and forest-data-directory.
These override statements can be done in an override function in the app_specific.rb file
The text was updated successfully, but these errors were encountered: