We have an application that uses a multi-tenant database setup, which means each tenant has their own database. Currently, this package always runs the migrations when running php artisan migrate. We don't want this table migrated in the central database but in the tenant database. Currently, I cannot prevent it from running.
Most packages give the user the option to publish the migrations and then run then when needed, I think this package should follow this convention.
We have an application that uses a multi-tenant database setup, which means each tenant has their own database. Currently, this package always runs the migrations when running
php artisan migrate
. We don't want this table migrated in the central database but in the tenant database. Currently, I cannot prevent it from running.Most packages give the user the option to publish the migrations and then run then when needed, I think this package should follow this convention.