Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

upcoming Rails 6 multi-database #2

Closed
rpbaltazar opened this issue Jan 3, 2020 · 7 comments
Closed

upcoming Rails 6 multi-database #2

rpbaltazar opened this issue Jan 3, 2020 · 7 comments

Comments

@rpbaltazar
Copy link
Contributor Author

influitive/apartment#629

@jean-francois-labbe
Copy link

@rpbaltazar hello, I use apartment in production with rails 6.0.2.1 and could help you with some pull requests if needed.
I tried your version but I'm getting the error described here: #3

Let me know if you need help

@rpbaltazar
Copy link
Contributor Author

Hi @jean-francois-labbe sounds good. I'm planning to go over a few things over the weekend and see what i can start doing with the read/write databases for rails 6. I'll update this issue with the findings.
I'm more than happy to have some more people involved in this

@rpbaltazar
Copy link
Contributor Author

rpbaltazar commented Feb 18, 2020

@jean-francois-labbe I've created a rails-6-demo from a boilerplate repo I found.
I've added the latest ros-apartment gem and tried the read/write replica feature in rails 6. I have not found any issues in this sample app.
It looks like its working and I have not encountered any issues.

@rpbaltazar
Copy link
Contributor Author

Closing this issue for now as we're running rails 6 without any known issues.

@marksiemers
Copy link
Contributor

@rpbaltazar - We are looking to switch to this fork of apartment and upgrade to rails 6.

Since this gem requires the original aparment, the gemspec there is still locking rails < 6.0 Is there a recommended way to unlock that?

@rpbaltazar
Copy link
Contributor Author

This actually does not require the original gem. require: 'apartment' is needed because the gem name does not match the main module but it is entirely independent. In fact there is a ticket proposing to detach from the original fork

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

No branches or pull requests

3 participants