Improve default behavior if environment configuration is not set
CoSApp uses a configuration file, ~/.cosapp.d/cosapp_config.json. This file seems to be created automatically in most normal situations, based upon $USERNAME and/or $USER. However, there are environments, such as specialized VM containers, where those environment variables are not set. (Maybe there are environments where the locations are not writeable?) In that case, any time an CoSApp System object is instantiated, the containing program will throw an error.
The workaround is to manually place the above file in the right place. This is not too difficult, but it is an extra deployment step in those types of environments (that has to be remembered), and the error message isn't clear what to do.
My recommendation is to not throw. (Maybe default the userid to something else if $USER isn't available.) Alternatively, the exception message should show the detailed file/location/format for that config file.