Error when starting "node app.js"

[geronimoooooooo]

I receive an error when I try to start with "node app.js".
Sails loads successfully and I get the information how to start on port: 1337 but in the end there is something wrong with the Redis connection to 127.0.0.1:6379.
The redis db comes with the project?

I use nodejs 0.10 on win2008 server x64.

Waiting...
verbose: Binding route :: get /gist/:id/FeatureServer/:layer/:method
verbose: Binding route :: get /gist/:id/FeatureServer/:layer
verbose: Binding route :: get /gist/:id/FeatureServer
verbose: Binding route :: get /gist/:id
verbose: Binding route :: get /gist/raw/:id
verbose: Binding route :: get /gist/raw/:id/:layer
verbose: Binding route :: get /gist
verbose: Binding route :: get /gist/:id/preview
verbose: Binding route :: get /github/
verbose: Binding route :: get /github/:user
verbose: Binding route :: get /github/:user/:repo
verbose: Binding route :: get /github/:user/:repo/FeatureServer
verbose: Binding route :: get /github/:user/:repo/FeatureServer/:layer
verbose: Binding route :: get /github/:user/:repo/FeatureServer/:layer/:method
verbose: Binding route :: get /github/:user/:repo/:file
verbose: Binding route :: get /github/:user/:repo/:file/FeatureServer
verbose: Binding route :: get /github/:user/:repo/:file/FeatureServer/:layer
verbose: Binding route :: get /github/:user/:repo/:file/FeatureServer/:layer/:method
verbose: Binding route :: get /github/:user/:repo/:file/preview
verbose: Binding route :: get /sample
debug: Lowering sails...
verbose: Sent kill signal to grunt child process...

events.js:72
throw er; // Unhandled 'error' event
^
Error: Redis connection to 127.0.0.1:6379 failed - connect ECONNREFUSED
at RedisClient.on_error (C:\Users\Administrator\Documents\GitHub\koop\node_modules\redis\index.js:163:24)
at Socket. (C:\Users\Administrator\Documents\GitHub\koop\node_modules\redis\index.js:86:14)
at Socket.EventEmitter.emit (events.js:95:17)
at net.js:441:14
at process._tickDomainCallback (node.js:459:13)

[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