melv1n
melv1n
Same request with same use case, so +1
I guess not, but [this Github project](https://github.com/samuraisam/pyapns) has proxy support on its feature list. So I would suggest giving that one a go first.
This would be either two things: - You're not sending the JSON payload properly (mostly a format issue, see APNS reference at Apple Developer portal). - The client is not...
That sounds like a lot of maintenance in one file. Why don't just create a pushd folder per app and start seperate daemons for each of them? If you need...
You need to uncomment this part and configure the required certificates in the iOS developer portal: `#uncomment for dev env #gateway: 'gateway.sandbox.push.apple.com' #address: 'feedback.sandbox.push.apple.com'` `# #Uncomment to use same host...
I think you mean by the api part, that you want to send a payload to a specific subscriber id. There is already a ticket for: #31. Just look at...
Read the ticket carefully. The creator tells why he'd chosen to do that by design. Pushd isn't designed to do just that.
Found the problem. It has to do with console logging. The cause lies with the console logging which it's expecting. When you start pushd in console, put as a background...
This is the debug trace for the node /usr/bin/coffee pushd.coffee process. This whole trace is from performing the first curl (and only) curl command after you start pushd via normal...
Btw. it would be nice if the normal startup (sudo coffee pushd.coffee) would do the same as the command above. Create two logs, one log with confirmed events and one...