1
# Redis configuration file example
3
# By default Redis does not run as a daemon. Use 'yes' if you need it.
4
# Note that Redis will write a pid file in /var/run/redis.pid when daemonized.
7
# When run as a daemon, Redis write a pid file in /var/run/redis.pid by default.
8
# You can specify a custom pid file location here.
9
pidfile /var/run/redis.pid
11
# Accept connections on the specified port, default is 6379
14
# If you want you can bind a single interface, if the bind option is not
15
# specified all the interfaces will listen for connections.
19
# Close the connection after a client is idle for N seconds (0 to disable)
22
# Save the DB on disk:
24
# save <seconds> <changes>
26
# Will save the DB if both the given number of seconds and the given
27
# number of write operations against the DB occurred.
29
# In the example below the behaviour will be to save:
30
# after 900 sec (15 min) if at least 1 key changed
31
# after 300 sec (5 min) if at least 10 keys changed
32
# after 60 sec if at least 10000 keys changed
37
# The filename where to dump the DB
40
# For default save/load DB in/from the working directory
41
# Note that you must specify a directory not a file name.
44
# Set server verbosity to 'debug'
46
# debug (a lot of information, useful for development/testing)
47
# notice (moderately verbose, what you want in production probably)
48
# warning (only very important / critical messages are logged)
51
# Specify the log file name. Also 'stdout' can be used to force
52
# the demon to log on the standard output. Note that if you use standard
53
# output for logging but daemonize, logs will be sent to /dev/null
56
# Set the number of databases. The default database is DB 0, you can select
57
# a different one on a per-connection basis using SELECT <dbid> where
58
# dbid is a number between 0 and 'databases'-1
61
################################# REPLICATION #################################
63
# Master-Slave replication. Use slaveof to make a Redis instance a copy of
64
# another Redis server. Note that the configuration is local to the slave
65
# so for example it is possible to configure the slave to save the DB with a
66
# different interval, or to listen to another port, and so on.
68
# slaveof <masterip> <masterport>
70
################################## SECURITY ###################################
72
# Require clients to issue AUTH <PASSWORD> before processing any other
73
# commands. This might be useful in environments in which you do not trust
74
# others with access to the host running redis-server.
76
# This should stay commented out for backward compatibility and because most
77
# people do not need auth (e.g. they run their own servers).
79
# requirepass foobared
81
################################### LIMITS ####################################
83
# Set the max number of connected clients at the same time. By default there
84
# is no limit, and it's up to the number of file descriptors the Redis process
85
# is able to open. The special value '0' means no limts.
86
# Once the limit is reached Redis will close all the new connections sending
87
# an error 'max number of clients reached'.
91
# Don't use more memory than the specified amount of bytes.
92
# When the memory limit is reached Redis will try to remove keys with an
93
# EXPIRE set. It will try to start freeing keys that are going to expire
94
# in little time and preserve keys with a longer time to live.
95
# Redis will also try to remove objects from free lists if possible.
97
# If all this fails, Redis will start to reply with errors to commands
98
# that will use more memory, like SET, LPUSH, and so on, and will continue
99
# to reply to most read-only commands like GET.
101
# WARNING: maxmemory can be a good idea mainly if you want to use Redis as a
102
# 'state' server or cache, not as a real DB. When Redis is used as a real
103
# database the memory usage will grow over the weeks, it will be obvious if
104
# it is going to use too much memory in the long run, and you'll have the time
105
# to upgrade. With maxmemory after the limit is reached you'll start to get
106
# errors for write operations, and this may even lead to DB inconsistency.
110
############################### ADVANCED CONFIG ###############################
112
# Glue small output buffers together in order to send small replies in a
113
# single TCP packet. Uses a bit more CPU but most of the times it is a win
114
# in terms of number of queries per second. Use 'yes' if unsure.
added
removed
t/redis.conf.base
