

#Install redis local install
The following would install and start three separate instances of Redis as a service: Redis-server -service-install -loglevel verboseĪnd then later, in the same document, another example: Upon successful installation a success message will be displayed and Redis will exit. The service will be configured as Autostart and will be launched as "NT AUTHORITY\NetworkService". Arguments after this are passed in the order they occur to Redis when the service is launched. This must be the first argument on the redis-server command line.
#Install redis local zip file
Go to the releases and you can get a ZIP file containing the relevant files as well as a Word document called RedisService.docx with the following instructions: You will not need to restart the service for changes to take effect. There you'll find a config file called nf, which you can edit to set up additional instances, use different paths than I specified in steps 2 & 3, etc.

Create another folder at c:\redis\inst1.Copy all extracted binaries to c:\redis\bin.Download and extract the Redis binaries from the 2.6 branch.So you'll need to download binaries from 2 branches in order to get all the necessary bits.
#Install redis local code
Should not be affected by the Redis version, and the code in the 2.4īranch should work with the Redis 2.6 binaries. So far the RedisWatcher is not carried over to 2.6. I won't go into it.) Fortunately they've provided all the binaries you need, just not all in one place. (I tried building RedisWatcher myself per their instructions, but the required Wix Toolset managed to mess up my system pretty good. They claim it is production-ready, but they haven't exactly packaged it up neatly for installation on a server, especially if you want to run their RedisWatcher service to keep an eye on it, which is recommended. MSOpenTech's seems to be the only port that is actively trying to keep up with the latest and greatest Redis. If you want to install MSOpenTech's latest port of Redis, on a Windows server, watched over by a Windows Service, without having to build anything yourself, read on.
