Missed updated config file for migrations

Author: Dave Redfern

config/migrations.php

@@ -4,44 +4,59 @@
 
     /*
     |--------------------------------------------------------------------------
-    | Migration Repository Table
+    | Entity Manager Migrations Configuration
     |--------------------------------------------------------------------------
     |
-    | This table keeps track of all the migrations that have already run for
-    | your application. Using this information, we can determine which of
-    | the migrations on disk haven't actually been run in the database.
+    | Each entity manager can have a custom migration configuration. Provide
+    | the name of the entity manager as the key, then duplicate the settings.
+    | This will allow generating custom migrations per EM instance and not have
+    | collisions when executing them.
     |
     */
-    'table'     => 'migrations',
-    /*
-    |--------------------------------------------------------------------------
-    | Migration Directory
-    |--------------------------------------------------------------------------
-    |
-    | This directory is where all migrations will be stored
-    |
-    */
-    'directory' => database_path('migrations'),
-    /*
-    |--------------------------------------------------------------------------
-    | Migration Namespace
-    |--------------------------------------------------------------------------
-    |
-    | This namespace will be used on all migrations
-    |
-    */
-    'namespace' => 'Database\\Migrations',
-    /*
-    |--------------------------------------------------------------------------
-    | Migration Repository Table
-    |--------------------------------------------------------------------------
-    |
-    | Tables which are filtered by Regular Expression. You optionally
-    | exclude or limit to certain tables. The default will
-    | filter all tables.
-    |
-    */
-    'schema'    => [
-        'filter' => '/^(?).*$/'
-    ]
+    'default' => [
+        /*
+        |--------------------------------------------------------------------------
+        | Migration Repository Table
+        |--------------------------------------------------------------------------
+        |
+        | This table keeps track of all the migrations that have already run for
+        | your application. Using this information, we can determine which of
+        | the migrations on disk haven't actually been run in the database.
+        |
+        */
+        'table'     => 'migrations',
+        /*
+        |--------------------------------------------------------------------------
+        | Migration Directory
+        |--------------------------------------------------------------------------
+        |
+        | This directory is where all migrations will be stored for this entity
+        | manager. User different directories for each entity manager.
+        |
+        */
+        'directory' => database_path('migrations'),
+        /*
+        |--------------------------------------------------------------------------
+        | Migration Namespace
+        |--------------------------------------------------------------------------
+        |
+        | This namespace will be used on all migrations. To prevent collisions, add
+        | the entity manager name (connection name).
+        |
+        */
+        'namespace' => 'Database\\Migrations',
+        /*
+        |--------------------------------------------------------------------------
+        | Migration Repository Table
+        |--------------------------------------------------------------------------
+        |
+        | Tables which are filtered by Regular Expression. You optionally
+        | exclude or limit to certain tables. The default will
+        | filter all tables.
+        |
+        */
+        'schema'    => [
+            'filter' => '/^(?!password_resets|failed_jobs).*$/'
+        ]
+    ],
 ];