Hi,
It would be nice if you could set somewhere the database to use by rapns.
I'm working on some projects and all of them are going to use rapns on the same machine, and my problem comes with the "only 1 instance of rapns" restriction.
My solution: I have a "master" rails app which I only use to configure and start rapns (daemon mode, e.g. "$ rapns production"). This app connects to the "rapns" database.
My other apps have their own database, and also access the rapns one. When I have to send a notification, I'm having to specify the rapns database connection with something like:
Rapns::App.establish_connection "rapns_#{Rails.env}"
Rapns::Notification.establish_connection "rapns_#{Rails.env}"
before creating the notification, to let ActiveRecord to find rapns classes.
So it would be great if you could specify somewhere the database configuration where rapns model objects live, in the initializer, for instance.
Hi,
It would be nice if you could set somewhere the database to use by rapns.
I'm working on some projects and all of them are going to use rapns on the same machine, and my problem comes with the "only 1 instance of rapns" restriction.
My solution: I have a "master" rails app which I only use to configure and start rapns (daemon mode, e.g. "$ rapns production"). This app connects to the "rapns" database.
My other apps have their own database, and also access the rapns one. When I have to send a notification, I'm having to specify the rapns database connection with something like:
Rapns::App.establish_connection "rapns_#{Rails.env}"
Rapns::Notification.establish_connection "rapns_#{Rails.env}"
before creating the notification, to let ActiveRecord to find rapns classes.
So it would be great if you could specify somewhere the database configuration where rapns model objects live, in the initializer, for instance.