From 5b3669daaa94b19dc245d9b25f825e598088ae92 Mon Sep 17 00:00:00 2001 From: James Moger Date: Wed, 16 Apr 2014 00:23:21 -0400 Subject: Documentation --- src/site/tickets_setup.mkd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/site/tickets_setup.mkd') diff --git a/src/site/tickets_setup.mkd b/src/site/tickets_setup.mkd index c098f4c1..aeecbeb1 100644 --- a/src/site/tickets_setup.mkd +++ b/src/site/tickets_setup.mkd @@ -28,7 +28,7 @@ Your ticket journals are persisted to `id/{shard}/{id}/journal.json`. These jou Your ticket journals are persisted to a Redis data store. *Make sure you configure your Redis instance for durability!!* This particular service is highly-scalable and very fast. Plus you can use all of the power of Redis replication, should you want. -The main drawback to this service is that Redis is primarily a Unix tool and works best on a Unix server. While there is a Windows port, sort-of maintained by Microsoft, it is not actively updated. +The main drawback to this service is that Redis is primarily a Unix tool and works best on a Unix server. Microsoft is engaged with the Redis community and they do maintain a semi-active port of Redis for Windows servers. tickets.redis.url = redis://(:{password}@){hostname}:{port}(/{databaseId}) -- cgit v1.2.3