Tuesday, May 19, 2015
Thanks for replying.
-- I'm now deciding on the best approach to take.
I was all set up to use act_as_tenant and devise.
But after reading some of Ryans posts (https://leanpub.com/multi-tenancy-rails) , I'm not sure this is the best way.
Any insights on tried and true real world implementations of multi tenancy?
PS.: I'm looking around for something scope based
PS.: I'm looking around for something scope based
2015-05-17 14:26 GMT-03:00 Chris Lerum <chris.lerum@gmail.com>:
You seem to answer your own question: you already know it's an architectural requirement, so I'd suggest including it from the beginning.--
On Friday, May 15, 2015 at 3:50:15 PM UTC-4, Leandro França wrote:Hi there,
I'm building a new app that will need to have multi tenancy features and I'd like to hear some opinions.
When do you guys think is a good time to add multi tenancy feature?
Do you usually add it from the ground up or just at a later stage?Thanks,
Leandro
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/c5d3a318-2159-4977-8b84-09fe6c450337%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAAt6bOqDK9Tj83drg30r0MwG41gBrfnRP%3D%2BkxTDUdSAD_Pnj_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment