Redis+ What's news?
Redis+ supports new features.
Expiring Key Event
Expiring key event can retrieves key and value.
Why we needs it because is not possible to get value of key when Expired Event. You just retrieves the key.
So, For implements like as sync or processing value, needs just the Redis's Expiring Event.
First, you should be set to subscribe keyspace-events
> config set notify-keyspace-events KEA > PSUBSCRIBE '__key*__:expiring'
When keys expiring before expired.
SET mykey "you can get key and value" ex 3
3 seconds past. Subscribed mykey is
1) "pmessage" 2) "__key*__:expiring" 3) "__keyevent@0__:expiring" 4) "mykey" 5) "you can get key and value" << IMPORTANT: You got it is value of key.
This is original readme of redis
Where to find complete Redis documentation?
This README is just a fast "quick start" document. You can find more detailed documentation at http://redis.io
Redis can be compiled and used on Linux, OSX, OpenBSD, NetBSD, FreeBSD. We support big endian and little endian architectures.
It may compile on Solaris derived systems (for instance SmartOS) but our support for this platform is "best effort" and Redis is not guaranteed to work as well as in Linux, OSX, and *BSD there.
It is as simple as:
You can run a 32 bit Redis binary using:
% make 32bit
After building Redis is a good idea to test it, using:
% make test
Fixing problems building 32 bit binaries
If after building Redis with a 32 bit target you need to rebuild it with a 64 bit target, or the other way around, you need to perform a "make distclean" in the root directory of the Redis distribution.
In case of build errors when trying to build a 32 bit binary of Redis, try the following steps:
Install the packages libc6-dev-i386 (also try g++-multilib).
Try using the following command line instead of "make 32bit":
make CFLAGS="-m32 -march=native" LDFLAGS="-m32"
Selecting a non-default memory allocator when building Redis is done by setting
MALLOC environment variable. Redis is compiled and linked against libc
malloc by default, with the exception of jemalloc being the default on Linux
systems. This default was picked because jemalloc has proven to have fewer
fragmentation problems than libc malloc.
To force compiling against libc malloc, use:
% make MALLOC=libc
To compile against jemalloc on Mac OS X systems, use:
% make MALLOC=jemalloc
Redis will build with a user friendly colorized output by default. If you want to see a more verbose output use the following:
% make V=1
To run Redis with the default configuration just type:
% cd src % ./redis-server
If you want to provide your redis.conf, you have to run it using an additional parameter (the path of the configuration file):
% cd src % ./redis-server /path/to/redis.conf
It is possible to alter the Redis configuration passing parameters directly as options using the command line. Examples:
% ./redis-server --port 9999 --slaveof 127.0.0.1 6379 % ./redis-server /etc/redis/6379.conf --loglevel debug
All the options in redis.conf are also supported as options using the command line, with exactly the same name.
Playing with Redis
You can use redis-cli to play with Redis. Start a redis-server instance, then in another terminal try the following:
% cd src % ./redis-cli redis> ping PONG redis> set foo bar OK redis> get foo "bar" redis> incr mycounter (integer) 1 redis> incr mycounter (integer) 2 redis>
You can find the list of all the available commands here:
In order to install Redis binaries into /usr/local/bin just use:
% make install
You can use "make PREFIX=/some/other/directory install" if you wish to use a different destination.
Make install will just install binaries in your system, but will not configure init scripts and configuration files in the appropriate place. This is not needed if you want just to play a bit with Redis, but if you are installing it the proper way for a production system, we have a script doing this for Ubuntu and Debian systems:
% cd utils % ./install_server.sh
The script will ask you a few questions and will setup everything you need to run Redis properly as a background daemon that will start again on system reboots.
You'll be able to stop and start Redis using the script named /etc/init.d/redis_, for instance /etc/init.d/redis_6379.
Note: by contributing code to the Redis project in any form, including sending a pull request via Github, a code fragment or patch via private email or public discussion groups, you agree to release your code under the terms of the BSD license that you can find in the COPYING file included in the Redis source distribution.
Please see the CONTRIBUTING file in this source distribution for more information.