If exists, import a config file to allow for overriding script variables. #20
Conversation
|
I like everything you have done. Have you found that the Also, it may seem minor, but I typically prefer the double bracket notation for |
|
What I did to check the local-ttl was to wireshark and look at what's on the wire. Without the local-ttl queries that ended up using adList had a TTL of 0. And that each time I did a I'll check out the double bracket notation. |
|
Cool. So I'm guessing that is 300 seconds? Is that just an arbitrary number or did you try out different values? |
If exists, import a config file to allow for overriding script variables.
|
Looks great. Let me know what you find out about the value to set. |
|
Yea, it's 300 seconds. I randomly picked a value to be honest. 5 minutes seems reasonable. Thank you for the merge. I'm trying to gear up for production use of the script/concept at work. |
|
No problem. It's a great addition. I would love to hear how you get it going at work and the response. Thanks! |
You can add your own config file to permanently set variables used in the gravity script. If the file exists, gravity.sh will detect it and apply your custom variables. This is useful so when there is an update to the gravity script, you do not need to adjust the variables every time.
To allow for minor variations of use of the script, parsing a config file could update some of the data locations.
In my case my
/etc/pihole/pihole.conflooks like this:This would make it so that I wouldn't need to modify future versions of the script. I could also create my own "sources" list and possibly not need to tweak the script.