README.md in certmeister-1.0.0 vs README.md in certmeister-1.0.1

@@ -13,16 +13,21 @@
 * Requests to delete certificates are only allowed when they originate from
   a secure operator network.
 
 This allows us the convenience of Puppet's autosign feature, without the horrendous security implications.
 
-This repository currently builds three gems:
+This repository currently builds two gems:
 
 * _certmeister_ - the CA, some off-the-shelf policy modules and an in-memory cert store
-* _certmeister-redis_ - a redis-backed store
 * _certmeister-rack_ - a rack application to provide an HTTP interface to the CA
 
+Only an in-memory store is provided. Others are available as separate gems:
+
+* [certmeister-dynamodb](https://github.com/sheldonh/certmeister-dynamodb)
+* [certmeister-pg](https://github.com/sheldonh/certmeister-pg)
+* [certmeister-redis](https://github.com/sheldonh/certmeister-redis)
+
 An example, using redis and rack and enforcing Hetzner PTY Ltd's policy, is available in [contrib/config.ru](contrib/config.ru).
 
 To hit the service:
 
 ```
@@ -32,22 +37,11 @@
     http://localhost:9292/ca/certificate/axl.starjuice.net
 ```
 
 ## Testing
 
-Because we test both certmeister and certmeister-redis with `rake spec`, you need redis up if you want to run the tests. It's easy:
-
-* Install redis-2.8.4 or later.
-* Start redis.
-* Run tests.
-* Stop redis.
-
 ```
-sudo yum install -y ansible
-sudo ansible-playbook -i contrib/hosts contrib/redis.yml
-redis-server --logfile /dev/null &
 rake spec
-kill %1; wait %1
 ```
 
 ## Releasing
 
 If you work at Hetzner and need to release new versions of the gems, do this