Future of milia

[jekuno]

In 2015 I accepted the invite of @dsaronin to continue his milia gem.

Starting from 2017 I did not manage to keep up with maintaining this gem for various reasons. Sorry for that!

I know this gem still is used in many projects so I want to invite all of you to join here and share ideas on how to find the best way to continue from here.

Right now I see the following options:

1. Continue with milia: I hand the ownership of the milia gem over to somebody new who feels to have the capacities and knowhow to maintain this gem. Please contact me or comment in this thread if you want to step into this.
2. Abandon milia: The milia users move over to a different gem. AFAIK the gem acts_as_tenant is the most popular multitenanting gem for Rails which has a shared database for all tenants.
   • Please feel free to add your insights here how the acts_as_tenant gem compares to milia to make the decision easier for readers of this post. @ErwinM, the owner of acts_as_tenant, feel free to write a few words yourself.
   • Also If anybody does or did move a project over to this or a different multitenanting gem please feel invited to share instructions on how to do so so that other users can build on that.

If there are more options worth to consider simply add them below.

Also thanks to @yshmarov for bringing that maintenance topic back to my attention in #88.

[yshmarov]

If you look into the used by, you will see that in 99% of cases the gem is used for educational purposes, specifically for a very popular course on udemy.

Looking into all the changes done in forks, the two most important ones are:

• support uuid
• basic rails 6 support

I think that if just basic rails 6 support is added to master, it will be good. This week I moved my massive SaaS application from Rails5 to Rails 6 and installed milia using this commit and it works well (just as before / as expected).

However, I would not recommend to work on adding any additional features to the gem.

[philsmy]

We use milia for a highly successful SaaS. At the moment we are on rails 5 but yes the issues hold us back. That being said, I think there is a place for this gem as it is slightly different in scope and features than anything else I can find. We’re starting a new saas service and actually using the commit you mention will use milia again.

On Sun, May 17, 2020 at 19:07 yashm notifications@github.com wrote:

If you look into the used by https://github.com/jekuno/milia/network/dependents?package_id=UGFja2FnZS0xOTcyNA%3D%3D, you will see that in 99% of cases the gem is used for educational purposes, specifically for a very popular course on udemy.

Looking into all the changes done in forks, https://github.com/jekuno/milia/networkthe two most important ones are:

• support uuid
• basic rails 6 support

I think that if just basic rails 6 support is added to master, it will be good. This week I moved my massive SaaS application from Rails5 to Rails 6 and installed milia using this commit https://github.com/indirect/milia/commit/e27d816dfb32df859e7a9160baabb3893680d799 and it works well (just as before / as expected).

However, I would not recommend to work on adding any additional features to the gem.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/jekuno/milia/issues/90#issuecomment-629773151, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAEALZDPCQGRAHXYZYSNHDRR6ZM5ANCNFSM4NDH6PZA .

-- Phil Smy twitter: http://twitter.com/psmy biz youtube: https://www.youtube.com/philsmy music youtube: https://www.youtube.com/user/sendaiphil facebook: https://www.facebook.com/philsmylife/

[yshmarov]

Not many answers... Anyway, no matter what, milia is still the most advanced, feature-rich single-database multitenancy gem and it should be minimally maintained! It's so depressing to see that the last commit was in 2017... @jekuno , would you still be able to merge PRs, just to keep the gem updated? Otherwise, transfer the gem to somebody that would minimally maintain it?

[yshmarov]

@Souravgoswami not the right place for your question.

[Justicea83]

It's really sad I there are comments dating back to 2020, and there's still no way forward.

[yshmarov]

The year is 2023 and we have 2 fantastic alternatives:

• https://github.com/ErwinM/acts_as_tenant
• https://github.com/citusdata/activerecord-multi-tenant 🎉

[philsmy]

Also - if I may be so bold - I have done a port of Milia to work on Rails 7. You can find that here: https://github.com/philsmy/philia

[lorint]

Thank you for keeping the dream alive, @philsmy!

[jekuno]

As written in the beginning of this thread my intention is to transfer milia to a new owner.

I hand the ownership of the milia gem over to somebody new who feels to have the capacities and knowhow to maintain this gem. Please contact me or comment in this thread if you want to step into this.

Up to now, I did not get any applcations for this job. ;) However, I am very happy to read that @philsmy did a port to Rails 7.

Are you willing to maintain milia in future @philsmy or is anybody else open for that opportunity?

[philsmy]

@jekuno, I forked and renamed it. Which I know is not nice, but I wasn't (at the time) sure what else to do.

I am actively maintaining my fork because I use it in production (and it is the best solution I have found so far). I could bring it back into Milia proper if you were ok with that.

[jekuno]

Sounds great! I have sent you an email and already assigned collaborator permissions to you to get things rolling.

[philsmy]

Okie dokie! I'm in! I'm traveling now, but towards the end of next week, I will try to re-merge my Philia fork back into Milia, with my Rails 6 and Rails 7 branches.