anchor.diff:  
   # Command renaming.
   #
  -# It is possilbe to change the name of dangerous commands in a shared
  +# It is possible to change the name of dangerous commands in a shared
   # environment. For instance the CONFIG command may be renamed into something
  -# of hard to guess so that it will be still available for internal-use
  -# tools but not available for general clients.
  +# hard to guess so that it will still be available for internal-use tools
  +# but not available for general clients.
   #
   # Example:
   #
   # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
   #
  -# It is also possilbe to completely kill a command renaming it into
  +# It is also possible to completely kill a command by renaming it into
   # an empty string:
   #
   # rename-command CONFIG ""
  +#
  +# Please note that changing the name of commands that are logged into the
  +# AOF file or transmitted to slaves may cause problems.
   
   ################################### LIMITS ####################################
   
  -# Set the max number of connected clients at the same time. By default there
  -# is no limit, and it's up to the number of file descriptors the Redis process
  -# is able to open. The special value '0' means no limits.
  +# Set the max number of connected clients at the same time. By default
  +# this limit is set to 10000 clients, however if the Redis server is not
  +# able to configure the process file limit to allow for the specified limit
  +# the max number of allowed clients is set to the current file limit
  +# minus 32 (as Redis reserves a few file descriptors for internal uses).
   # Once the limit is reached Redis will close all the new connections sending
   # an error 'max number of clients reached'.
   #
  -# maxclients 128
   <% if @conf_maxclients != 'UNSET' %>
   maxclients <%= @conf_maxclients %>
   <% end %>
  
positive.code: 
  ############################## APPEND ONLY MODE ###############################
  
  # By default Redis asynchronously dumps the dataset on disk. If you can live
  # with the idea that the latest records will be lost if something like a crash
  # happens this is the preferred way to run Redis. If instead you care a lot
  # about your data and don't want to that a single record can get lost you should
  # enable the append only mode: when this mode is enabled Redis will append
  # every write operation received in the file appendonly.aof. This file will
  # be read on startup in order to rebuild the full dataset in memory.
  #
  # Note that you can have both the async dumps and the append only file if you
  # like (you have to comment the "save" statements above to disable the dumps).
  # Still if append only mode is enabled Redis will load the data from the
  # log file at startup ignoring the dump.rdb file.
  #
  # IMPORTANT: Check the BGREWRITEAOF to check how to rewrite the append
  # log file in background when it gets too big.
  
  appendonly <%= @conf_appendonly %>
  
  
negative.code: #save 60 10000
  <% else %>
    <% if @conf_save != 'UNSET' %>
  save <%= @conf_save %>
    <% else %>
  save 900 1
  save 300 10
  save 60 10000
    <% end %>
  <% end %>
  
  # By default Redis will stop accepting writes if RDB snapshots are enabled
  # (at least one save point) and the latest background save failed.
  # This will make the user aware (in an hard way) that data is not persisting
  # on disk properly, otherwise chances are that no one will notice and some
  # distater will happen.
  #
  # If the background saving process will start working again Redis will
  # automatically allow writes again.
  #
  # However if you have setup your proper monitoring of the Redis server
  # and persistence, you may want to disable this feature so that Redis will
  # continue to work as usually even if there are problems with disk,
  # permissions, and so forth.
  stop-writes-on-bgsave-error yes
  
  # Compress string objects using LZF when dump .rdb databases?
  # For default that's set to 'yes' as it's almost always a win.
  