CODEWITHSUNDEEP
ruby-on-rails
sonxurxo
sonxurxo

Reputation: 5718

Rails app as backend for multiple apps

We're developing a Rails app that will serve as a backend for multiple apps. The Rails app will have a web CMS that will let admin users to manage their mobile apps (one admin user can have 1..N mobile apps).

The same Rails app will also serve as an API for those mobile apps. The mobile apps are completely separated one from each others, not sharing any data among them. We have users with different roles (global_admin which manages his app in the CMS, place_manager which manages his place in the app within the CMS, and users of the mobile app). These users are not shared between apps (if a user signs up in a mobile app, he will be able to log in only in that app; so if he wants to log in another mobile app he needs to register again).

Which is the best approach to achieve this? We are thinking about:

Thank you in advance

Upvotes: 0

Views: 258

Answers (4)

fylooi
fylooi

Reputation: 3870

The API/API users scenario looks like a situation for multi-tenancy in which each app runs as a separate instance. You can look at something like Apartment for database level multitenancy, or Milia for app level multitenancy.

Database level is generally easier to manage, but you will need a workaround for the global admin requirement.

Upvotes: 2

Bart Jedrocha
Bart Jedrocha

Reputation: 11570

I think Option 1 would work well in your case. You can setup a has_many :through relationship between apps and users that will contain information regarding the user's role for that particular application (assuming only one role per user per application).

With this approach the workflow would be a bit different than what you describe though. If the user is not registered at all (i.e. no record with that email exists), they will need to signup (email + password) at which point you'll create the user record (with hashed password) and setup the association to the mobile application. If the user IS already registered, you don't want them entering a new password again, you'll simply want to setup the association. This can be handled via first_or_create. Hope this helps.

Upvotes: 0

user1073501
user1073501

Reputation:

I suggest the following approach if you would like to use a single rails application for multiple mobile apps.

  1. For users you can have different API returning different kinds of users, specific to the application requirement.
  2. Use STI to differentiate users for each apps(in this way, you could have only a single table for users but different models)

Upvotes: 1

Ely
Ely

Reputation: 11174

These users are not shared between apps (if a user signs up in a mobile app, he will be able to log in only in that app; so if he wants to log in another mobile app he needs to register again).

In my opinion these are three different Rails apps. Obviously the apps have nothing in common, in particular no data is shared.

Upvotes: 0

Related Questions