From d40a8874585fb5f8e45a938473840acdf9a2a538 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Samuel=20=C5=A0tancl?= Date: Sun, 6 Oct 2019 20:32:10 +0200 Subject: [PATCH] Section no longer necessary --- .../difference-between-this-package-and-others.blade.md | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/source/v2/difference-between-this-package-and-others.blade.md b/docs/source/v2/difference-between-this-package-and-others.blade.md index c090c29..34bfe23 100644 --- a/docs/source/v2/difference-between-this-package-and-others.blade.md +++ b/docs/source/v2/difference-between-this-package-and-others.blade.md @@ -41,11 +41,3 @@ Everything else happens automatically in the background: This means that you can also integrate with any packages you would normally use, without any difficulties. We believe that this seamless approach to multi-tenancy is consistent with Laravel's "developer happiness from download to deploy". - -## Which one should you use? - -If you want to implement multi-tenancy yourself by writing package-specific tenant-aware code, use tenancy/multi-tenant. - -If you want to be assisted in writing your own tenancy implementation, use tenancy/tenancy (currently in alpha). - -If you want to focus on writing your application instead of tenancy implementations, and have no problems trying to integrate other packages, use stancl/tenancy.