anchor.diff:  # Specify the syslog identity.
   # syslog-ident redis
   
  -# Specify the syslog facility.  Must be USER or between LOCAL0-LOCAL7.
  +# Specify the syslog facility. Must be USER or between LOCAL0-LOCAL7.
   # syslog-facility local0
   
   # Set the number of databases. The default database is DB 0, you can select
  
positive.code: #
  # slaveof <masterip> <masterport>
  
  # If the master is password protected (using the requirepass configuration
  # directive below) it is possible to tell the slave to authenticate before
  # starting the replication synchronization process, otherwise the master will
  # refuse the slave request.
  #
  # masterauth <master-password>
  
  # When a slave lost the connection with the master, or when the replication
  # is still in progress, the slave can act in two different ways:
  #
  # 1) if slave-serve-stale-data is set to 'yes' (the default) the slave will
  #    still reply to client requests, possibly with out of data data, or the
  #    data set may just be empty if this is the first synchronization.
  #
  # 2) if slave-serve-stale data is set to 'no' the slave will reply with
  #    an error SYNC with master in progress to all the kind of commands
  #    but to INFO and SLAVEOF.
  #
  slave-serve-stale-data yes
  
  ################################## SECURITY ###################################
  
  # Require clients to issue AUTH <PASSWORD> before processing any other
  # commands.  This might be useful in environments in which you do not trust
  # others with access to the host running redis.
  #
  # This should stay commented out for backward compatibility and because most
  # people do not need auth (e.g. they run their own servers).
  #
  # Warning: since Redis is pretty fast an outside user can try up to
  # 150k passwords per second against a good box. This means that you should
  # use a very strong password otherwise it will be very easy to break.
  #
  <% if @redis_password %>
  requirepass <%= @redis_password %>
  <% end %>
  
  # Command renaming.
  #
  # It is possilbe 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.
  #
  # Example:
  #
  # rename-command CONFIG b840fc02d524045429941cc15f59e41cb7be6c52
  #
  # It is also possilbe to completely kill a command renaming it into
  # an empty string:
  #
  # rename-command CONFIG 
  
  ################################### 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.
  # Once the limit is reached Redis will close all the new connections sending
  # an error 'max number of clients reached'.
  #
  # maxclients 128
  <% if @real_redis_max_clients %>
  maxclients <%= @real_redis_max_clients %>
  <% end %>
  
  # Don't use more memory than the specified amount of bytes.
  # When the memory limit is reached Redis will try to remove keys with an
  # EXPIRE set. It will try to start freeing keys that are going to expire
  # in little time and preserve keys with a longer time to live.
  # Redis will also try to remove objects from free lists if possible.
  #
  # If all this fails, Redis will start to reply with errors to commands
  # that will use more memory, like SET, LPUSH, and so on, and will continue
  # to reply to most read-only commands like GET.
  #
  # WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
  # 'state' server or cache, not as a real DB. When Redis is used as a real
  # database the memory usage will grow over the weeks, it will be obvious if
  # it is going to use too much memory in the long run, and you'll have the time
  # to upgrade. With maxmemory after the limit is reached you'll start to get
  # errors for write operations, and this may even lead to DB inconsistency.
  #
  # maxmemory <bytes>
  maxmemory <%= @redis_max_memory %>
  
  # MAXMEMORY POLICY: how Redis will select what to remove when maxmemory
  # is reached? You can select among five behavior:
  #
  # volatile-lru -> remove the key with an expire set using an LRU algorithm
  # allkeys-lru -> remove any key accordingly to the LRU algorithm
  # volatile-random -> remove a random key with an expire set
  # allkeys->random -> remove a random key, any key
  # volatile-ttl -> remove the key with the nearest expire time (minor TTL)
  # noeviction -> don't expire at all, just return an error on write operations
  #
  # Note: with all the kind of policies, Redis will return an error on write
  #       operations, when there are not suitable keys for eviction.
  #
  #       At the date of writing this commands are: set setnx setex append
  
negative.code: #
  # The DB will be written inside this directory, with the filename specified
  # above using the 'dbfilename' configuration directive.
  # 
  # The Append Only File will also be created inside this directory.
  # 
  # Note that you must specify a directory here, not a file name.
  dir /var/lib/redis/<%= @redis_port %>
  
  