The way I architect such Apps is by using centralized scope based
authorization. It keeps the App clean and avoid bugs like dev forgot to
scope the records in controller - controller can ONLY operate on records
that are permitted for the current user. If somebody tries to access
resource outsid
On 14 March 2017 at 00:28, fugee ohu wrote:
>
>
> On Monday, March 13, 2017 at 7:51:03 PM UTC-4, Walter Lee Davis wrote:
>>
>> There are a number of different ways you can manage this. One popular
>> approach is to use the Apartment gem to create what is known as the
>> "multi-tenant" database pat
On Monday, March 13, 2017 at 7:51:03 PM UTC-4, Walter Lee Davis wrote:
>
> There are a number of different ways you can manage this. One popular
> approach is to use the Apartment gem to create what is known as the
> "multi-tenant" database pattern. See if that term gets you closer to what
> y
On Monday, March 13, 2017 at 7:51:03 PM UTC-4, Walter Lee Davis wrote:
>
> There are a number of different ways you can manage this. One popular
> approach is to use the Apartment gem to create what is known as the
> "multi-tenant" database pattern. See if that term gets you closer to what
> yo
There are a number of different ways you can manage this. One popular approach
is to use the Apartment gem to create what is known as the "multi-tenant"
database pattern. See if that term gets you closer to what your are looking for.
One database (or at least one schema) per site is the usual me
i have the idea to use the same database for multiple sites but i guess
each site needs it's own database in addition? Anyone can guide me?
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Talk" group.
To unsubscribe from this group and stop receivin
6 matches
Mail list logo
