To ensure that application code does not become polluted with code that loads configuration, a mechanism is needed that can specify and import a configuration.
A simple mechanism would be to have an environment variable CORTO_CONFIG that can point to either a file or a directory. If it points to a file, then that file will be loaded with corto_load- this means that the file extension must be available in driver/ext. If it points to a directory, corto will load all files in that directory.
If the environment variable is not set, no configuration is loaded.
To make it easier to specify a configuration, the tool should have an option --config that allows specifying a value for $CORTO_CONFIG.
To ensure that application code does not become polluted with code that loads configuration, a mechanism is needed that can specify and import a configuration.
A simple mechanism would be to have an environment variable
CORTO_CONFIGthat can point to either a file or a directory. If it points to a file, then that file will be loaded withcorto_load- this means that the file extension must be available indriver/ext. If it points to a directory, corto will load all files in that directory.If the environment variable is not set, no configuration is loaded.
To make it easier to specify a configuration, the tool should have an option
--configthat allows specifying a value for$CORTO_CONFIG.