Error when starting "node app.js" about koop

[chelm]

Ahh totally. Let me add a better check for Redis. If no redis-server is running locally it dies (bug), so it should default to its local cache storage.

Also: Im planning switching out the caching/storage to use levelDB which should eliminate this issue and Redis altogether.

[geronimoooooooo]

big thx!
Just to clarify: In order to run koop right now, I need to install and run a redis?

[chelm]

@geronimoooooooo I just pushed a fix. If you pull down the latest you dont need to have Redis, it will use a local object hash storage that gets erased every time you stop the koop server. So for testing this in fine but in any sort of production env you'd want to use Redis.

Also, i added a flag to start up to manually tell Koop to use redis (in the readme). so to start with a redis backend:

node app.js --redis=true