Currently, program creates a log file at a hardcoded path to avoid errors with config so that it may log any of said errors. If the user chooses not to alter the default name of the log, this poses no issue, but it's far from an ideal solution.
Other possibilities include:
[ ] Loading log conf from a dedicated log.conf file (however, there would be two config files for separate entities)
[ ] Creating a separate log just for config errors
[ ] Assume the user is smart enough to understand a small config file 4head
[ ] Try to load the config file first just to set logging, throw error if file doesn't exist
Currently, program creates a log file at a hardcoded path to avoid errors with config so that it may log any of said errors. If the user chooses not to alter the default name of the log, this poses no issue, but it's far from an ideal solution.
Other possibilities include: