Currently the information for connecting to the SOCKS5 proxy is passed using command-line arguments (e.g. -h and -p, for host and port respectively) when running the main program. I think it would be useful if these could be stored and read from a configuration file instead. The command line arguments can take precedent over the configuration file (if passed) but the config file should be the default method of passing this information. The information can be stored in a simple file format such as .env, .yaml and .json where it'll be read/written as needed.
Currently the information for connecting to the SOCKS5 proxy is passed using command-line arguments (e.g.
-h
and-p
, for host and port respectively) when running the main program. I think it would be useful if these could be stored and read from a configuration file instead. The command line arguments can take precedent over the configuration file (if passed) but the config file should be the default method of passing this information. The information can be stored in a simple file format such as.env
,.yaml
and.json
where it'll be read/written as needed.