Configuration file should be taken as an argument #34
Description
Currently for convenience, a configuration file is generated on the first run and is always consumed from the same working directory as the binary is executed. This implementation was to make project separation easier but comes with an overlooked issue where the executable file could/should be placed outside of a project directory.
This is a tracking issue alongside #32 to implement override for every configuration functions.