Fresh install using multi databases

[malsgit]

Hello, some knowledgeable person should be able to solve this??

Just done a fresh install of Laravel 10, Jetstream, using PHP8.2 and Valet on a Mac....

gone through the installation documents, then followed this
https://spatie.be/docs/laravel-multitenancy/v3/installation/using-multiple-databases
to use multiple databases.
ran the migration for the landlord to create the tenants table, create a tenant manually...
then ran

php artisan tenants:artisan "migrate --database=tenant"

and ended up with the following error.....? any ideas of what is causing this, I've read the instructions 5 times and still can't see what I have missed out.....

Spatie\Multitenancy\Exceptions\InvalidConfiguration 

`SwitchTenantDatabaseTask` fails because `multitenancy.tenant_database_connection_name` is `null` or equals to `multitenancy.landlord_database_connection_name`.

at vendor/spatie/laravel-multitenancy/src/Exceptions/InvalidConfiguration.php:16
  12▕     }
  13▕ 
  14▕     public static function tenantConnectionIsEmptyOrEqualsToLandlordConnection(): self
  15▕     {
➜  16▕         return new static("`SwitchTenantDatabaseTask` fails because `multitenancy.tenant_database_connection_name` is `null` or equals to `multitenancy.landlord_database_connection_name`.");
  17▕     }
  18▕ 
  19▕     public static function invalidAction(string $actionName, string $configuredClass, string $actionClass): self
  20▕     {

   +20 vendor frames 

21  artisan:35
   Illuminate\Foundation\Console\Kernel::handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))

[malsgit]

Solved it, it isn't clear in the documentation, to replace the following code in config>multitenancy.php

'tenant_database_connection_name' => null, 

 'landlord_database_connection_name' => null,

to

 'tenant_database_connection_name' =>  'tenant',

  'landlord_database_connection_name' => 'landlord',

It seems all the other steps where you are changing code you have code blocks, which makes it really clear....

it was just lost in Configuring the database connection in docs

No doubt looking at all the closed issues, with the same issue, which isn't a bug they will have more than likely missed this important step, like I did..