-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loading config from /etc/cow folder #328
Comments
Good suggestion. I'll implement this recently. |
@fzerorubigd let's switch to this issue to discuss. What about the following behavior:
|
I think it should be a config directory, not the config file. the |
@cyfdecyf |
I took a look at nginx and dnsmasq's options. For nginx you can specify config file, while for dnsmasq you can either set config file or config directory. I'd prefer to specify the config file, as only this file is mandatory for running cow. This also allows users to specify different config files in the same directory. (I do this when debugging cow.) I agree with you for removing
For Hope my company work goes smooth so I can finish this feature this week. |
@cyfdecyf starting work on |
Also load stat/blocked/direct default from directory containing config file.
…file. Also load stat/blocked/direct default from directory containing config file.
Its helpful to try to load config from
/etc/cow
folder, IF the ~/.cow is not available.The text was updated successfully, but these errors were encountered: