Update _default.yml #8
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think it's there because I found it there in the packages. Not sure if it's the best one tough. I'll have a look. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
for your consideration...
reading the tinyproxy man page, the default locations tinyproxy checks for configuration is:
/etc/tinyproxy/tinyproxy.conf,/var/run/tinyproxy/tinyproxy.pid,/var/log/tinyproxy/tinyproxy.logWhen running this playbook on an OS that does not have a specific configuration listed in the vars folder, the config file is created at a location that tinyproxy when run as a service, is not picked up, and the service runs with the default configuration that comes with the package install.
is there some other reason the default is in this location? otherwise, I think we need to merge #3 so that it can be overridden by users.