[FEATURE REQUEST] read-only redis.conf option

[GoogleCodeExporter]

This option would disallow direct writes, and only allow write operations
through replication (similar to how it is done in MySQL).

This is useful for a (yet to be fully implemented) VIP-based failover
solution and to keep developers from writing directly to Redis slaves.

Original issue reported on code.google.com by ryan.a.l...@gmail.com on 24 Nov 2009 at 3:49

[GoogleCodeExporter]

not a bad idea indeed... I'll think a bit more about it but sounds cool

Original comment by anti...@gmail.com on 23 Aug 2010 at 4:07

[GoogleCodeExporter]

I'm also interested by this feature. Having only one point of write-access 
protected by password and number of read-only clients will be something cool :) 
But I think the more general mechanism will be implement whitelist or blacklist 
of commands.

Original comment by jo...@zhr.pl on 21 Jan 2011 at 6:49

[GoogleCodeExporter]

any updates on this one? Really useful feature that I have to implement in a 
client library instead of a config setting

Original comment by nike.gur...@gmail.com on 4 Nov 2011 at 10:37

[GoogleCodeExporter]

I would also greatly appreciate such an option.

Currently the only other way to achieve this is to use a different set of 
usernames/passwords on a slave, and point the client to the slave rather than 
the master.

Original comment by karen.et...@gmail.com on 10 Jan 2013 at 5:47