From 8b47a464a6966709acb88b5851d7b3846b460bb0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Samuel=20=C5=A0tancl?= Date: Sat, 21 Dec 2019 14:57:48 +0100 Subject: [PATCH] Nova migrations --- docs/source/v2/nova.blade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/v2/nova.blade.md b/docs/source/v2/nova.blade.md index 029a82e..d05df90 100644 --- a/docs/source/v2/nova.blade.md +++ b/docs/source/v2/nova.blade.md @@ -12,7 +12,7 @@ To use Nova inside of the tenant part of your application, do the following: ```none php artisan vendor:publish --tag=nova-migrations ``` - > Note: Unfortunately, Nova will still be adding its migrations to your central migrations. This is something we'd like to solve in the future. +- Prevent Nova from adding its migrations to your central migrations by adding `Nova::ignoreMigrations()` to `NovaServiceProvider::boot()` (Don't do this if you want to use Nova [both in the central & tenant parts]({{ $page->link('universal-routes') }}) of the app.) - Add the `'tenancy'` middleware group to your `nova.middleware` config. Example: ```php 'middleware' => [