You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Artiasan commands have an env option to run with a given env (e.g. --env=testing). When I run artisan tenants:migrate-fresh --env=testing the worng database gets refreshed
Steps to reproduce
Have a .env and a .env.testing with different db configurations / tenants
Run artisan tenants:migrate-fresh --env=testing
The testing db didn't get refreshed
Expected behavior
The testing db and tenants get refreshed and the local/default db is left untouched
Laravel version
Laravel 10.48.26
stancl/tenancy version
3.8.5
The text was updated successfully, but these errors were encountered:
Bug description
Artiasan commands have an env option to run with a given env (e.g.
--env=testing
). When I runartisan tenants:migrate-fresh --env=testing
the worng database gets refreshedSteps to reproduce
artisan tenants:migrate-fresh --env=testing
Expected behavior
The testing db and tenants get refreshed and the local/default db is left untouched
Laravel version
Laravel 10.48.26
stancl/tenancy version
3.8.5
The text was updated successfully, but these errors were encountered: