From 4ff1629e70f98a55ad74605f3fca977535cf1a17 Mon Sep 17 00:00:00 2001 From: Adrian Marin Date: Fri, 2 Aug 2024 01:00:25 +0300 Subject: [PATCH] wip --- docs/3.0/guides/acts_as_tenant_integration.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/docs/3.0/guides/acts_as_tenant_integration.md b/docs/3.0/guides/acts_as_tenant_integration.md index 8608042a..0cef8eb2 100644 --- a/docs/3.0/guides/acts_as_tenant_integration.md +++ b/docs/3.0/guides/acts_as_tenant_integration.md @@ -19,15 +19,14 @@ Check out the [acts_as_tenant](https://github.com/ErwinM/acts_as_tenant) documen ::: ## Installation -___ To use it, add it to your Gemfile: ```ruby gem 'acts_as_tenant' +``` ## Tenant -___ Let's create model for tenant. We are using `Account` as our tenant. @@ -87,7 +86,6 @@ end ::: ## Setting the current tenant -___ There are three ways to set the current tenant but we be using the subdomain to lookup the current tenant. Since Avo has it's own `Application Controller` so there is no point in setting the tenant in Rails default `Application Controller` but we will set it there as well just to be safe site and also we might have some other pages other than Admin Dashboard supported by Avo. @@ -135,7 +133,6 @@ end Now, whenever we navigate to https://sahsantoshh.example.com/ the tenant & the tenant_id will be set to **sahsantoshh**. - ## Move existing data to model We might have to many users and other records which needs to be associated with `Account`.