Skip to content
This repository has been archived by the owner on Mar 9, 2018. It is now read-only.

Multiple databases support #183

Open
sonxurxo opened this issue Nov 28, 2013 · 2 comments
Open

Multiple databases support #183

sonxurxo opened this issue Nov 28, 2013 · 2 comments

Comments

@sonxurxo
Copy link

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.

@mattconnolly
Copy link
Contributor

Could you make a simple API in your "master" app (the one with the rapns database) so the other apps simply make a HTTP request to it, and it's controller action is to save the notification so rapns can send it?

@ileitch
Copy link
Owner

ileitch commented Jan 7, 2014

I'd accept a PR for this, but it's low priority for me personally.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants