Ruby on Rails Wednesday, January 17, 2018



On Wednesday, January 17, 2018 at 3:13:19 PM UTC-5, Walter Lee Davis wrote:
That depends. Do you want your multiple blogs to each have their own set of users, with none of them able to see any besides their "own" blogs? That's the real problem that multi-tenancy solves. It's for Software As A Service-size problems, where you have thousands of users and thousands of blogs, and everyone thinks it their own server.

Walter

> On Jan 17, 2018, at 2:21 PM, fugee ohu <fuge...@gmail.com> wrote:
>
> To build a multi blog  platform I would want to use multi-tenancy?
> ng 
> --
> 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-ta...@googlegroups.com.
> To post to this group, send email to rubyonra...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/be53e8cc-48a4-4730-a351-ea9f4cb03bb8%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


I was looking for a blog gem mountable at the model level but I still haven't found one that works so I was thinking i can use something else in a multi-tenant setup Of all the blog gems the only one I found that mounts on the model was blogit but it needs updating I couldn't bundle it I don't need multi-tenancy to offer users subdomains, I can do that with regular rails routing, just to solve this problem

--
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/84613e9e-c97b-47b8-8570-685a5d7d36e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment