Flynn Redis

commands.txt

# create a redis app
flynn create --remote "" redis

# create a release using the latest (at the time of writing) Docker Redis image
flynn -a redis release add -f config.json "https://registry.hub.docker.com?name=redis&id=868be653dea3ff6082b043c0f34b95bb180cc82ab14a18d9d6b8e27b7929762c"

# scale the server to one process. This may time out initially as the server pulls the image, but watch "flynn -a redis ps" and should come up.
flynn -a redis scale server=1

# redis should now be running in the cluster at redis.discoverd:6379
flynn -a redis run redis-cli -h redis.discoverd -p 6379
redis.discoverd:6379> PING
PONG

# note that although the container has a data volume, they are not currently sticky so restarting the container will get a new data directory. This will be fixed when we have a Redis appliance / sticky volumes.

config.json

{
  "processes": {
    "server": {
      "cmd": ["redis-server"],
      "data": true,
      "ports": [{
        "port": 6379,
        "proto": "tcp",
        "service": {
          "name": "redis",
          "create": true,
          "check": { "type": "tcp" }
        }
      }]
    }
  }
}

Data persistence is not working?

@sevazhidkov No, unfortunately at this time persistent storage is not supported.See issue: flynn/flynn#1345