redis_orm 0.7 → 0.8

data/test/indices_test.rb

@@ -1,63 +0,0 @@
-require File.dirname(File.expand_path(__FILE__)) + '/test_helper.rb'
-
-describe "check indices" do
-  it "should change index accordingly to the changes in the model" do
-    user = User.new :first_name => "Robert", :last_name => "Pirsig"
-    user.save
-
-    u = User.find_by_first_name("Robert")
-    u.id.should == user.id
-
-    u = User.find_by_first_name_and_last_name("Robert", "Pirsig")
-    u.id.should == user.id
-
-    u.first_name = "Chris"
-    u.save
-
-    User.find_by_first_name("Robert").should == nil
-
-    User.find_by_first_name_and_last_name("Robert", "Pirsig").should == nil
-
-    User.find_by_first_name("Chris").id.should == user.id
-    User.find_by_last_name("Pirsig").id.should == user.id
-    User.find_by_first_name_and_last_name("Chris", "Pirsig").id.should == user.id    
-  end
-
-  it "should change index accordingly to the changes in the model (test #update_attributes method)" do
-    user = User.new :first_name => "Robert", :last_name => "Pirsig"
-    user.save
-
-    u = User.find_by_first_name("Robert")
-    u.id.should == user.id
-
-    u = User.find_by_first_name_and_last_name("Robert", "Pirsig")
-    u.id.should == user.id
-
-    u.update_attributes :first_name => "Christofer", :last_name => "Robin"
-
-    User.find_by_first_name("Robert").should == nil
-    User.find_by_last_name("Pirsig").should == nil
-    User.find_by_first_name_and_last_name("Robert", "Pirsig").should == nil
-
-    User.find_by_first_name("Christofer").id.should == user.id
-    User.find_by_last_name("Robin").id.should == user.id
-    User.find_by_first_name_and_last_name("Christofer", "Robin").id.should == user.id    
-  end
-  
-  it "should create case insensitive indices too" do
-    ou = OmniUser.new :email => "GERMAN@Ya.ru", :uid => 2718281828
-    ou.save
-    
-    OmniUser.count.should == 1
-    OmniUser.find_by_email("german@ya.ru").should be
-    OmniUser.find_all_by_email("german@ya.ru").count.should == 1
-    
-    OmniUser.find_by_email_and_uid("german@ya.ru", 2718281828).should be
-    OmniUser.find_all_by_email_and_uid("german@ya.ru", 2718281828).count.should == 1
-
-    OmniUser.find_by_email("geRman@yA.rU").should be
-    OmniUser.find_all_by_email_and_uid("GerMan@Ya.ru", 2718281828).count.should == 1
-        
-    OmniUser.find_all_by_email_and_uid("german@ya.ru", 2718281829).count.should == 0
-  end
-end

data/test/modules/belongs_to_model_within_module.rb

@@ -1,6 +0,0 @@
-module BelongsToModelWithinModule
-  class Reply < RedisOrm::Base
-    property :body, String, :default => "test"
-    belongs_to :article, :as => :essay
-  end
-end

data/test/modules/has_many_model_within_module.rb

@@ -1,11 +0,0 @@
-module HasManyModelWithinModule
-  class SpecialComment < RedisOrm::Base
-    property :body, String, :default => "test"
-    belongs_to :brochure, :as => :book
-  end
-
-  class Brochure < RedisOrm::Base
-    property :title, String
-    has_many :special_comments
-  end
-end

data/test/options_test.rb

@@ -1,226 +0,0 @@
-require File.dirname(File.expand_path(__FILE__)) + '/test_helper.rb'
-
-describe "test options" do
-  before(:each) do
-    @album = Album.new
-    @album.title = "my 1st album"
-    @album.save
-
-    @album.should be
-    @album.title.should == "my 1st album"
-
-    @photo1 = Photo.new :image => "facepalm.jpg", :image_type => "jpg", :checked => true
-    @photo1.save
-    @photo1.should be
-    @photo1.image.should == "facepalm.jpg"
-    @photo1.image_type.should == "jpg"
-
-    @photo2 = Photo.new :image => "boobs.png", :image_type => "png", :inverted => false
-    @photo2.save
-    @photo2.should be
-    @photo2.image.should == "boobs.png"
-    @photo2.image_type.should == "png"
-  end
-
-  it "should behave like expected for #find and #find! methods (nb exceptions with #find! are tested in exceptions_test.rb file)" do
-    Album.find(@album.id).should == @album
-    Album.find!(@album.id).should == @album
-    
-    Album.find(:first).should == @album
-    Album.find!(:first).should == @album
-    
-    Album.find(:all, :limit => 1).size.should == 1
-    Album.find!(:all, :limit => 1).size.should == 1
-  end
-
-  it "should return correct array when :limit and :offset options are provided" do
-    @album.photos.count.should == 0
-
-    @album.photos.all(:limit => 2, :offset => 0).should == []
-
-    @album.photos << [@photo1, @photo2]
-
-    @album.photos.all(:limit => 0, :offset => 0).should == []
-    @album.photos.all(:limit => 1, :offset => 0).size.should == 1
-    @album.photos.all(:limit => 2, :offset => 0).size.should == 2 #[@photo1, @photo2]
-
-    @album.photos.all(:limit => 0, :offset => 0).should == []
-    @album.photos.all(:limit => 1, :offset => 1).size.should == 1 # [@photo2]
-    @album.photos.all(:limit => 2, :offset => 2).should == []
-
-    @album.photos.find(:all, :limit => 1, :offset => 1).size.should == 1
-    
-    Photo.find(:all).size.should == 2
-
-    Photo.find(:first).should == @photo1
-    Photo.find(:last).should == @photo2
-    
-    Photo.find(:all, :conditions => {:image => "facepalm.jpg"}).size.should == 1
-    Photo.find(:all, :conditions => {:image => "boobs.png"}).size.should == 1
-
-    Photo.find(:all, :conditions => {:image => "facepalm.jpg", :image_type => "jpg"}).size.should == 1
-    Photo.find(:all, :conditions => {:image => "boobs.png", :image_type => "png"}).size.should == 1
-        
-    Photo.find(:first, :conditions => {:image => "facepalm.jpg"}).should == @photo1
-    Photo.find(:first, :conditions => {:image => "boobs.png"}).should == @photo2
-    
-    Photo.find(:first, :conditions => {:image => "facepalm.jpg", :image_type => "jpg"}).should == @photo1
-    Photo.find(:first, :conditions => {:image => "boobs.png", :image_type => "png"}).should == @photo2
-    
-    Photo.find(:last, :conditions => {:image => "facepalm.jpg"}).should == @photo1
-    Photo.find(:last, :conditions => {:image => "boobs.png"}).should == @photo2
-    
-    Photo.find(:last, :conditions => {:image => "facepalm.jpg", :image_type => "jpg"}).should == @photo1
-    Photo.find(:last, :conditions => {:image => "boobs.png", :image_type => "png"}).should == @photo2
-  end
-
-  it "should accept options for #first and #last methods" do
-    Photo.first(:conditions => {:image => "facepalm.jpg"}).should == @photo1
-    Photo.first(:conditions => {:image => "boobs.png"}).should == @photo2
-    
-    Photo.last(:conditions => {:image => "facepalm.jpg", :image_type => "jpg"}).should == @photo1
-    Photo.last(:conditions => {:image => "boobs.png", :image_type => "png"}).should == @photo2
-  end
-
-  it "should correctly save boolean values" do
-    $redis.hgetall("photo:#{@photo1.id}")["inverted"].should == "true"
-    $redis.hgetall("photo:#{@photo2.id}")["inverted"].should == "false"
-
-    @photo1.inverted.should == true 
-    @photo2.inverted.should == false
-        
-    $redis.zrange("photo:inverted:true", 0, -1).should include(@photo1.id.to_s)
-    $redis.zrange("photo:inverted:false", 0, -1).should include(@photo2.id.to_s)
-    
-    $redis.hgetall("photo:#{@photo1.id}")["checked"].should == "true"
-    $redis.hgetall("photo:#{@photo2.id}")["checked"].should == "false"
-    
-    @photo1.checked.should == true
-    @photo2.checked.should == false
-    
-    $redis.zrange("photo:checked:true", 0, -1).should include(@photo1.id.to_s)
-    $redis.zrange("photo:checked:false", 0, -1).should include(@photo2.id.to_s)
-  end
-
-  it "should search on bool values properly" do
-    Photo.find(:all, :conditions => {:checked => true}).size.should == 1
-    Photo.find(:all, :conditions => {:checked => true}).first.id.should == @photo1.id
-    Photo.find(:all, :conditions => {:checked => false}).size.should == 1
-    Photo.find(:all, :conditions => {:checked => false}).first.id.should == @photo2.id
-    
-    Photo.find(:all, :conditions => {:inverted => true}).size.should == 1
-    Photo.find(:all, :conditions => {:inverted => true}).first.id.should == @photo1.id
-    Photo.find(:all, :conditions => {:inverted => false}).size.should == 1
-    Photo.find(:all, :conditions => {:inverted => false}).first.id.should == @photo2.id
-  end
-
-  it "should return correct array when :order option is provided" do
-    Photo.all(:order => "asc").map{|p| p.id}.should == [@photo1.id, @photo2.id]
-    Photo.all(:order => "desc").map{|p| p.id}.should == [@photo2.id, @photo1.id]
-
-    Photo.all(:order => "asc", :limit => 1).map{|p| p.id}.should == [@photo1.id]
-    Photo.all(:order => "desc", :limit => 1).map{|p| p.id}.should == [@photo2.id]
-
-    Photo.all(:order => "asc", :limit => 1, :offset => 1).map{|p| p.id}.should == [@photo2.id]
-    Photo.all(:order => "desc", :limit => 1, :offset => 1).map{|p| p.id}.should == [@photo1.id]
-
-    # testing #find method
-    Photo.find(:all, :order => "asc").map{|p| p.id}.should == [@photo1.id, @photo2.id]
-    Photo.find(:all, :order => "desc").map{|p| p.id}.should == [@photo2.id, @photo1.id]
-
-    Photo.find(:all, :order => "asc", :limit => 1).map{|p| p.id}.should == [@photo1.id]
-    Photo.find(:all, :order => "desc", :limit => 1).map{|p| p.id}.should == [@photo2.id]
-
-    Photo.find(:first, :order => "asc", :limit => 1, :offset => 1).id.should == @photo2.id
-    Photo.find(:first, :order => "desc", :limit => 1, :offset => 1).id.should == @photo1.id
-
-    Photo.find(:last, :order => "asc").id.should == @photo2.id
-    Photo.find(:last, :order => "desc").id.should == @photo1.id
-    
-    @album.photos.count.should == 0
-    @album.photos.all(:limit => 2, :offset => 0).should == []
-    @album.photos << @photo2
-    @album.photos << @photo1
-
-    @album.photos.all(:order => "asc").map{|p| p.id}.should == [@photo2.id, @photo1.id]
-    @album.photos.all(:order => "desc").map{|p| p.id}.should == [@photo1.id, @photo2.id]
-    @album.photos.all(:order => "asc", :limit => 1).map{|p| p.id}.should == [@photo2.id]
-    @album.photos.all(:order => "desc", :limit => 1).map{|p| p.id}.should == [@photo1.id]
-    @album.photos.all(:order => "asc", :limit => 1, :offset => 1).map{|p| p.id}.should == [@photo1.id]
-    @album.photos.all(:order => "desc", :limit => 1, :offset => 1).map{|p| p.id}.should == [@photo2.id]
-
-    @album.photos.find(:all, :order => "asc").map{|p| p.id}.should == [@photo2.id, @photo1.id]
-    @album.photos.find(:all, :order => "desc").map{|p| p.id}.should == [@photo1.id, @photo2.id]
-    
-    @album.photos.find(:first, :order => "asc").id.should == @photo2.id
-    @album.photos.find(:first, :order => "desc").id.should == @photo1.id
-
-    @album.photos.find(:last, :order => "asc").id.should == @photo1.id
-    @album.photos.find(:last, :order => "desc").id.should == @photo2.id
-        
-    @album.photos.find(:last, :order => "desc", :offset => 2).should == nil
-    @album.photos.find(:first, :order => "desc", :offset => 2).should == nil
-    
-    @album.photos.find(:all, :order => "asc", :limit => 1, :offset => 1).map{|p| p.id}.should == [@photo1.id]
-    @album.photos.find(:all, :order => "desc", :limit => 1, :offset => 1).map{|p| p.id}.should == [@photo2.id]
-  end
-
-  it "should delete associated records when :dependant => :destroy in *has_many* assoc" do
-    @album.photos << [@photo1, @photo2]
-
-    @album.photos.count.should == 2
-
-    Photo.count.should == 2
-    @album.destroy
-    Photo.count.should == 0
-    Album.count.should == 0
-  end
-
-  it "should *NOT* delete associated records when :dependant => :nullify or empty in *has_many* assoc" do
-    Photo.count.should == 2
-
-    category = Category.new
-    category.title = "cats"
-    category.save
-
-    Category.count.should == 1
-
-    category.photos << [@photo1, @photo2]
-    category.photos.count.should == 2
-
-    category.destroy
-
-    Photo.count.should == 2
-    Category.count.should == 0
-  end
-
-  it "should delete associated records when :dependant => :destroy and leave them otherwise in *has_one* assoc" do
-    user = User.new
-    user.name = "Dmitrii Samoilov"
-    user.save
-    user.should be
-
-    user.photo = @photo1
-
-    user.photo.id.should == @photo1.id
-
-    User.count.should == 1
-    Photo.count.should == 2
-    user.destroy
-    Photo.count.should == 1
-    User.count.should == 0
-  end
-
-  it "should delete link to associated record when record was deleted" do
-    @album.photos << [@photo1, @photo2]
-
-    @album.photos.count.should == 2
-
-    Photo.count.should == 2
-    @photo1.destroy
-    Photo.count.should == 1
-    
-    @album.photos.count.should == 1
-    @album.photos.size.should == 1
-  end
-end

data/test/polymorphic_test.rb

@@ -1,65 +0,0 @@
-require File.dirname(File.expand_path(__FILE__)) + '/test_helper.rb'
-
-describe "check polymorphic property" do
-  it "should provide proper associations and save records correctly for has_one/belongs_to polymorphic" do
-    book = Book.new :title => "Permutation City", :author => "Egan Greg", :price => 1529
-    book.save
-
-    giftcard = Giftcard.create :title => "Happy New Year!"
-
-    ci1 = CatalogItem.create :title => giftcard.title
-    ci1.resource = giftcard
-    
-    ci2 = CatalogItem.create :title => book.title
-    ci2.resource = book
-    
-    CatalogItem.count.should == 2
-    [ci1, ci2].collect{|ci| ci.title}.should == [giftcard.title, book.title]
-    
-    ci1.resource.title.should == giftcard.title
-    ci2.resource.title.should == book.title
-    
-    Book.first.catalog_item.should be
-    Book.first.catalog_item.id.should == ci2.id
-    
-    Giftcard.first.catalog_item.should be
-    Giftcard.first.catalog_item.id.should == ci1.id
-  end
-  
-  it "should provide proper associations and save records correctly for has_many/belongs_to polymorphic" do
-    country = Country.create :name => "Ukraine"
-    city = City.create :name => "Lviv"
-    
-    person = Person.create :name => "german"
-    person.location = country
-    
-    Person.first.location.id.should == country.id
-    City.first.people.count.should == 0
-    Country.first.people.count.should == 1
-    Country.first.people[0].id.should == person.id
-    
-    person = Person.first
-    person.location = city
-    
-    Person.first.location.id.should == city.id
-    City.first.people.count.should == 1
-    City.first.people[0].id.should == person.id
-    Country.first.people.count.should == 0
-  end
-  
-  it "should delete records properly" do
-    country = Country.create :name => "Ukraine"
-    person = Person.create :name => "german"
-    person.location = country
-    
-    Person.first.location.id.should == country.id
-    Country.first.people.count.should == 1
-    Country.first.people[0].id.should == person.id
-    
-    person.destroy
-    Person.count.should == 0
-    $redis.hgetall("user:#{person.id}").should == {}
-    $redis.zrank("user:ids", person.id).should == nil
-    Country.first.people.count.should == 0
-  end
-end

data/test/redis.conf

@@ -1,417 +0,0 @@
-# Redis configuration file example
-
-# Note on units: when memory size is needed, it is possible to specifiy
-# it in the usual form of 1k 5GB 4M and so forth:
-#
-# 1k => 1000 bytes
-# 1kb => 1024 bytes
-# 1m => 1000000 bytes
-# 1mb => 1024*1024 bytes
-# 1g => 1000000000 bytes
-# 1gb => 1024*1024*1024 bytes
-#
-# units are case insensitive so 1GB 1Gb 1gB are all the same.
-
-# By default Redis does not run as a daemon. Use 'yes' if you need it.
-# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
-daemonize no
-
-# When running daemonized, Redis writes a pid file in /var/run/redis.pid by
-# default. You can specify a custom pid file location here.
-pidfile redis.pid
-
-# Accept connections on the specified port, default is 6379.
-# If port 0 is specified Redis will not listen on a TCP socket.
-port 0
-
-# If you want you can bind a single interface, if the bind option is not
-# specified all the interfaces will listen for incoming connections.
-#
-# bind 127.0.0.1
-
-# Specify the path for the unix socket that will be used to listen for
-# incoming connections. There is no default, so Redis will not listen
-# on a unix socket when not specified.
-#
-unixsocket redis.sock
-
-# Close the connection after a client is idle for N seconds (0 to disable)
-timeout 300
-
-# Set server verbosity to 'debug'
-# it can be one of:
-# debug (a lot of information, useful for development/testing)
-# verbose (many rarely useful info, but not a mess like the debug level)
-# notice (moderately verbose, what you want in production probably)
-# warning (only very important / critical messages are logged)
-loglevel verbose
-
-# Specify the log file name. Also 'stdout' can be used to force
-# Redis to log on the standard output. Note that if you use standard
-# output for logging but daemonize, logs will be sent to /dev/null
-logfile stdout
-
-# To enable logging to the system logger, just set 'syslog-enabled' to yes,
-# and optionally update the other syslog parameters to suit your needs.
-# syslog-enabled no
-
-# Specify the syslog identity.
-# syslog-ident redis
-
-# 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
-# a different one on a per-connection basis using SELECT <dbid> where
-# dbid is a number between 0 and 'databases'-1
-databases 2
-
-################################ SNAPSHOTTING  #################################
-#
-# Save the DB on disk:
-#
-#   save <seconds> <changes>
-#
-#   Will save the DB if both the given number of seconds and the given
-#   number of write operations against the DB occurred.
-#
-#   In the example below the behaviour will be to save:
-#   after 900 sec (15 min) if at least 1 key changed
-#   after 300 sec (5 min) if at least 10 keys changed
-#   after 60 sec if at least 10000 keys changed
-#
-#   Note: you can disable saving at all commenting all the "save" lines.
-
-save 10 1
-save 300 10
-save 60 10000
-
-# Compress string objects using LZF when dump .rdb databases?
-# For default that's set to 'yes' as it's almost always a win.
-# If you want to save some CPU in the saving child set it to 'no' but
-# the dataset will likely be bigger if you have compressible values or keys.
-rdbcompression yes
-
-# The filename where to dump the DB
-dbfilename dump.rdb
-
-# The working directory.
-#
-# The DB will be written inside this directory, with the filename specified
-# above using the 'dbfilename' configuration directive.
-# 
-# Also the Append Only File will be created inside this directory.
-# 
-# Note that you must specify a directory here, not a file name.
-dir ./
-
-################################# REPLICATION #################################
-
-# Master-Slave replication. Use slaveof to make a Redis instance a copy of
-# another Redis server. Note that the configuration is local to the slave
-# so for example it is possible to configure the slave to save the DB with a
-# different interval, or to listen to another port, and so on.
-#
-# 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-server.
-#
-# 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.
-#
-# requirepass foobared
-
-# 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
-
-# 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 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
-#       incr decr rpush lpush rpushx lpushx linsert lset rpoplpush sadd
-#       sinter sinterstore sunion sunionstore sdiff sdiffstore zadd zincrby
-#       zunionstore zinterstore hset hsetnx hmset hincrby incrby decrby
-#       getset mset msetnx exec sort
-#
-# The default is:
-#
-# maxmemory-policy volatile-lru
-
-# LRU and minimal TTL algorithms are not precise algorithms but approximated
-# algorithms (in order to save memory), so you can select as well the sample
-# size to check. For instance for default Redis will check three keys and
-# pick the one that was used less recently, you can change the sample size
-# using the following configuration directive.
-#
-# maxmemory-samples 3
-
-############################## 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 no
-
-# 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 
-# 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
-# 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
-# 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
-# everysec.
-#
-# If unsure, use "everysec".
-
-# appendfsync always
-appendfsync everysec
-# appendfsync no
-
-# When the AOF fsync policy is set to always or everysec, and a background
-# saving process (a background save or AOF log background rewriting) is
-# performing a lot of I/O against the disk, in some Linux configurations
-# Redis may block too long on the fsync() call. Note that there is no fix for
-# this currently, as even performing fsync in a different thread will block
-# our synchronous write(2) call.
-#
-# In order to mitigate this problem it's possible to use the following option
-# that will prevent fsync() from being called in the main process while a
-# BGSAVE or BGREWRITEAOF is in progress.
-#
-# This means that while another child is saving the durability of Redis is
-# the same as "appendfsync none", that in pratical terms means that it is
-# possible to lost up to 30 seconds of log in the worst scenario (with the
-# default Linux settings).
-# 
-# If you have latency problems turn this to "yes". Otherwise leave it as
-# "no" that is the safest pick from the point of view of durability.
-no-appendfsync-on-rewrite no
-
-################################ VIRTUAL MEMORY ###############################
-
-# Virtual Memory allows Redis to work with datasets bigger than the actual
-# amount of RAM needed to hold the whole dataset in memory.
-# In order to do so very used keys are taken in memory while the other keys
-# are swapped into a swap file, similarly to what operating systems do
-# with memory pages.
-#
-# To enable VM just set 'vm-enabled' to yes, and set the following three
-# VM parameters accordingly to your needs.
-
-#vm-enabled no
-# vm-enabled yes
-
-# This is the path of the Redis swap file. As you can guess, swap files
-# can't be shared by different Redis instances, so make sure to use a swap
-# file for every redis process you are running. Redis will complain if the
-# swap file is already in use.
-#
-# The best kind of storage for the Redis swap file (that's accessed at random) 
-# is a Solid State Disk (SSD).
-#
-# *** WARNING *** if you are using a shared hosting the default of putting
-# the swap file under /tmp is not secure. Create a dir with access granted
-# only to Redis user and configure Redis to create the swap file there.
-#vm-swap-file /tmp/redis.swap
-
-# vm-max-memory configures the VM to use at max the specified amount of
-# RAM. Everything that deos not fit will be swapped on disk *if* possible, that
-# is, if there is still enough contiguous space in the swap file.
-#
-# With vm-max-memory 0 the system will swap everything it can. Not a good
-# default, just specify the max amount of RAM you can in bytes, but it's
-# better to leave some margin. For instance specify an amount of RAM
-# that's more or less between 60 and 80% of your free RAM.
-#vm-max-memory 0
-
-# Redis swap files is split into pages. An object can be saved using multiple
-# contiguous pages, but pages can't be shared between different objects.
-# So if your page is too big, small objects swapped out on disk will waste
-# a lot of space. If you page is too small, there is less space in the swap
-# file (assuming you configured the same number of total swap file pages).
-#
-# If you use a lot of small objects, use a page size of 64 or 32 bytes.
-# If you use a lot of big objects, use a bigger page size.
-# If unsure, use the default :)
-#vm-page-size 32
-
-# Number of total memory pages in the swap file.
-# Given that the page table (a bitmap of free/used pages) is taken in memory,
-# every 8 pages on disk will consume 1 byte of RAM.
-#
-# The total swap size is vm-page-size * vm-pages
-#
-# With the default of 32-bytes memory pages and 134217728 pages Redis will
-# use a 4 GB swap file, that will use 16 MB of RAM for the page table.
-#
-# It's better to use the smallest acceptable value for your application,
-# but the default is large in order to work in most conditions.
-#vm-pages 134217728
-
-# Max number of VM I/O threads running at the same time.
-# This threads are used to read/write data from/to swap file, since they
-# also encode and decode objects from disk to memory or the reverse, a bigger
-# number of threads can help with big objects even if they can't help with
-# I/O itself as the physical device may not be able to couple with many
-# reads/writes operations at the same time.
-#
-# The special value of 0 turn off threaded I/O and enables the blocking
-# Virtual Memory implementation.
-#vm-max-threads 4
-
-############################### ADVANCED CONFIG ###############################
-
-# Hashes are encoded in a special way (much more memory efficient) when they
-# have at max a given numer of elements, and the biggest element does not
-# exceed a given threshold. You can configure this limits with the following
-# configuration directives.
-#hash-max-zipmap-entries 512
-#hash-max-zipmap-value 64
-
-# Similarly to hashes, small lists are also encoded in a special way in order
-# to save a lot of space. The special representation is only used when
-# you are under the following limits:
-list-max-ziplist-entries 512
-list-max-ziplist-value 64
-
-# Sets have a special encoding in just one case: when a set is composed
-# of just strings that happens to be integers in radix 10 in the range
-# of 64 bit signed integers.
-# The following configuration setting sets the limit in the size of the
-# set in order to use this special memory saving encoding.
-set-max-intset-entries 512
-
-# Active rehashing uses 1 millisecond every 100 milliseconds of CPU time in
-# order to help rehashing the main Redis hash table (the one mapping top-level
-# keys to values). The hash table implementation redis uses (see dict.c)
-# performs a lazy rehashing: the more operation you run into an hash table
-# that is rhashing, the more rehashing "steps" are performed, so if the
-# server is idle the rehashing is never complete and some more memory is used
-# by the hash table.
-# 
-# The default is to use this millisecond 10 times every second in order to
-# active rehashing the main dictionaries, freeing memory when possible.
-#
-# If unsure:
-# use "activerehashing no" if you have hard latency requirements and it is
-# not a good thing in your environment that Redis can reply form time to time
-# to queries with 2 milliseconds delay.
-#
-# use "activerehashing yes" if you don't have such hard requirements but
-# want to free memory asap when possible.
-activerehashing yes
-
-################################## INCLUDES ###################################
-
-# Include one or more other config files here.  This is useful if you
-# have a standard template that goes to all redis server but also need
-# to customize a few per-server settings.  Include files can include
-# other files, so use this wisely.
-#
-# include /path/to/local.conf
-# include /path/to/other.conf