Multiple database setup issue about laravel-multitenancy

[masterix21]

Yes, I think you have already found the best solution: switching to environment variables, you'll retake full control of your code (using .env and phpunit.xml).

// config/multitenancy.php
'landlord_database_connection_name' => env('DB_CONNECTION_LANDLORD', 'landlord');
'tenant_database_connection_name' => env('DB_CONNECTION_TENANT', 'tenant'),

[masterix21]

Don't you ever change your landlord connection anyway if you switch from landlord to testing_landlord?

I tried to simulate your code: the SQLite migration for landlord works, but without switching the landlord connection to testing_landlord, my application can't switch to the right tenant database.

Why can't you use an environment variable to set up the landlord/tenant database connection? Should switch easier using .env and phpunit.xml.

Please help me to understand.

[sausin]

@masterix21 Thanks for your reply.

So the tests are run on the sqlite connection while I "use" the application in local environment on the mysql connection. The setup described in the original post worked before the referenced PR.

If there is a convenient way to continue using like before, that would be great. My workaround at the moment is to change the environment variables to get things to work.