-
Notifications
You must be signed in to change notification settings - Fork 92
Improve Heroku experience #33
Comments
Isn't it working OK, if you run it as a separate process on the Cedar stack? |
Is it safe to run multiple rapns workers on Heroku? Or will they compete with each other for reads and writes to the notification and feedback tables, or try to send multiple copies of the same notification to Apple? |
Yes it'll likely send multiple notifications. Are you wanting to send to multiple apps? Sent from my iPhone On 06/03/2012, at 9:05 PM, thrillcallreply@reply.github.com wrote:
|
No, a single app, but we just wanted to verify what the behavior would
|
ah ok. If you're concerned about throughput, there is a |
I believe this is resolved. Been running on Heroku Cedar for some time without issues, also with 2.0. |
Good to hear. |
@EpicDraws can you give pointers how were you able to run the rapns daemon on Cedar? Simply running |
@neebz trying adding this to your Procfile: |
@EpicDraws Can you describe the web dynos vs worker dynos required to get it working properly? Does it all run okay on the free tier with just a single dyno? |
I've just written a quick Heroku guide: https://github.com/ileitch/rapns/wiki/Heroku |
I get this error every time, and I'm not quite sure what to do. I get this both on Heroku and locally. Any ideas?
|
Have you added rapns to your Gemfile and ran 'bundle install?' |
Yes, of course - and Heroku does that each deploy as well. |
I was under the impression you may be new to Rails. That is pretty odd then. Does the Can you check rapns is even in the load path:
What version of bundler do you have? |
Oh, and you are using rapns >= 2.0.0 right? |
Ah, looks like it was 1.0.7 - I will upgrade and get back to you. The |
Okay, looks like that did it. I upgraded to 2.0.1, ran |
For Rapns to work properly you need a Worker dyno on Heroku. But the free tier does not support this. Is there any other way to get Rapns to send out notifications? For instance each time a notification is created? |
rapns needs to run seamlessly on Heroku. Where that's not possible; we need clear and simple instructions.
The text was updated successfully, but these errors were encountered: