Allow Cache Replacement Policy to be configured #84
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
alexjfisher
requested changes
Jan 21, 2018
templates/squid.conf.header.erb
Outdated
| @@ -10,6 +10,13 @@ memory_cache_shared <%= (@memory_cache_shared == 'on' || @memory_cache | |||
| <% end -%> | |||
| maximum_object_size_in_memory <%= @maximum_object_size_in_memory %> | |||
|
|
|||
| <% unless @cache_replacement_policy.nil? -%> | |||
There was a problem hiding this comment.
Since these are Strings and not Booleans, you can simplify this to just
<% if @cache_replacement_policy -%>
There was a problem hiding this comment.
everything done, something else to handle or ready to merge?
There was a problem hiding this comment.
Hi @SourceDoctor the comment @alexjfisher about the simpler if rather than unless .. nil? still stands.
traylenator
added
enhancement
traylenator
changed the title
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.
configure cache Replacement Policy to prefereed method