Juho Vähä-Herttua
Juho Vähä-Herttua
@Pourliver I tried to fix this in the latest 0.3.12 release, please try it out and let me know if it helped.
My guess is that the problem is your npm uses "--mirror" with git clone, but your git version is too old to support it. I think in the case of...
Probably an old Python version, multiprocessing module was introduced in Python 2.6. You could upgrade python as well, or alternatively try to get http://code.google.com/p/python-multiprocessing/ from somewhere. Unfortunately Node.js doesn't mix...
Try to comment out redis_socket and uncomment redis_port and redis_host.
Did the last comment fix your issue? It would be polite to close the issue if it did.
Cool, I will make a patch that changes the settings-sample.coffee to be less confusing.
Hmm, I wonder if this is a pushd issue or a Node.js issue, should check it out...
There hasn't been releases since adding the winston logging, so I could still change the winston support to be more configurable. Then you could define in your settings.coffee if you...
You should define it with a key. So in the message use '${var.text}' and send 'var.text=value' in your push notification.
We have a logging branch that has a bit more verbose logging at https://github.com/futurice/pushd/tree/logging so you can at least confirm that the messages are going through. You just need to...