anchor.diff:  
   ############################## 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.
  +# By default Redis asynchronously dumps the dataset on disk. This mode is
  +# good enough in many applications, but an issue with the Redis process or
  +# a power outage may result into a few minutes of writes lost (depending on
  +# the configured save points).
  +#
  +# The Append Only File is an alternative persistence mode that provides
  +# much better durability. For instance using the default data fsync policy
  +# (see later in the config file) Redis can lose just one second of writes in a
  +# dramatic event like a server power outage, or a single write if something
  +# wrong with the Redis process itself happens, but the operating system is
  +# still running correctly.
  +#
  +# AOF and RDB persistence can be enabled at the same time without problems.
  +# If the AOF is enabled on startup Redis will load the AOF, that is the file
  +# with the better durability guarantees.
  +#
  +# Please check http://redis.io/topics/persistence for more information.
   
   appendonly no
   
  -# The name of the append only file (default: appendonly.aof)
  -# appendfilename appendonly.aof
  +# The name of the append only file (default: "appendonly.aof")
  +
  +appendfilename "appendonly.aof"
   
   # The fsync() call tells the Operating System to actually write data on disk
  -# instead to wait for more data in the output buffer. Some OS will really flush
  +# instead to wait for more data in the output buffer. Some OS will really flush 
   # data on disk, some other OS will just try to do it ASAP.
   #
   # Redis supports three different modes:
   #
   # no: don't fsync, just let the OS flush the data when it wants. Faster.
   # always: fsync after every write to the append only log . Slow, Safest.
  -# everysec: fsync only if one second passed since the last fsync. Compromise.
  -#
  -# The default is everysec that's usually the right compromise between
  +# everysec: fsync only one time every second. Compromise.
  +#
  +# The default is "everysec", as that's usually the right compromise between
   # speed and data safety. It's up to you to understand if you can relax this to
  -# no that will will let the operating system flush the output buffer when
  +# "no" that will let the operating system flush the output buffer when
   # it wants, for better performances (but if you can live with the idea of
   # some data loss consider the default persistence mode that's snapshotting),
  -# or on the contrary, use always that's very slow but a bit safer than
  +# or on the contrary, use "always" that's very slow but a bit safer than
   # everysec.
   #
  -# If unsure, use everysec.
  +# More details please check the following article:
  +# http://antirez.com/post/redis-persistence-demystified.html
  +#
  +# If unsure, use "everysec".
   
   # appendfsync always
   appendfsync everysec
  
positive.code: ################################ LUA SCRIPTING  ###############################
  
  # Max execution time of a Lua script in milliseconds.
  # This prevents that a programming error generating an infinite loop will block
  # your server forever. Set it to 0 or a negative value for unlimited execution.
  lua-time-limit <%= @redis_lua_time_limit %>
  
  ################################## SLOW LOG ###################################
  
negative.code: # but just the time needed to actually execute the command (this is the only
  # stage of command execution where the thread is blocked and can not serve
  # other requests in the meantime).
  # 
  # You can configure the slow log with two parameters: one tells Redis
  # what is the execution time, in microseconds, to exceed in order for the
  # command to get logged, and the other parameter is the length of the
  