Ruby on Rails

Sunday, January 21, 2018, 5:28:17 PM, you wrote:


>> On Jan 20, 2018, at 10:44 PM, fugee ohu <fugee279@gmail.com> wrote:

>> is multitenancy only for apps that have users?

WLD> Maybe. It depends on how you define it. Think about Basecamp for
WLD> an example. Each user of that system logs into their own
WLD> subdomain and manages their own data, without ever being able to
WLD> access or see any other user's data. Yet if you are the owners of
WLD> Basecamp, you think of it as one big site, with many users. Each
WLD> user can make changes to the application that govern how it will
WLD> appear to their clients, and that doesn't affect another user's
WLD> clients' view of the site. Think about the most popular Gem in
WLD> this arena -- it's named Apartment. What does an apartment have?
WLD> Individual rooms where renters can change whatever they like
WLD> without affecting anyone else in the building. Yet the owner
WLD> thinks of it as one big building.

WLD> So it's philosophical first, and then practical. What is the
WLD> application you are trying to build? Is it meant for one client,
WLD> or many users, each with their own group of sub-users? Or something else?

WLD> Walter

Walter,

What's Basecamp?  It sounds like something I need.

Ralph