Unable to configure Api key dealer server, outdated documentation?

Hi, brilliant api, great job. This was missing in Travis for a a long time. I'm wondering how to configure it with some simple token inside. It is correct command for linux? `eval $(DEALER_HOST=localhost:8080./public/clients/algolia-keys-mac export)` Looks like my `.env` is broken.
Thanks a lot.
[Documentation](https://github.com/algolia/api-key-dealer/blob/prod/README.md) says:
```
# edit to `.env` and add
# - test_ADMIN
# - NOCTT5TZUU_ADMIN
# - UCX3XB3SH4_ADMIN
# - CTS_1_ADMIN_KEY
# - CTS_2_ADMIN_KEY

# Run tests
composer test
```

My setup:
Using ubuntu 18.04
php 7.4

```
cat .env
APP_ENV=local
APP_DEBUG=true
APP_TIMEZONE=UTC

DB_CONNECTION=sqlite

CACHE_DRIVER=file
QUEUE_DRIVER=sync

KEY_VALIDITY=1296000

test_ADMIN=abcdef
```

```
composer test
> phpunit
PHPUnit 7.5.15 by Sebastian Bergmann and contributors.

Warning - The configuration file did not pass validation!
The following problems have been detected:

Line 11:
- Element 'phpunit', attribute 'syntaxCheck': The attribute 'syntaxCheck' is not allowed.

Test results may not be as expected.

E 1 / 1 (100%)

Time: 41 ms, Memory: 6.00 MB

There was 1 error:

1) GenerationOfKeysTest::testTravisService
ErrorException: Trying to access array offset on value of type null

/home/ubuntu/api-key-dealer/vendor/illuminate/support/ServiceProvider.php:97
/home/ubuntu/api-key-dealer/vendor/illuminate/pagination/PaginationServiceProvider.php:16
/home/ubuntu/api-key-dealer/vendor/illuminate/container/BoundMethod.php:32
/home/ubuntu/api-key-dealer/vendor/illuminate/container/BoundMethod.php:90
/home/ubuntu/api-key-dealer/vendor/illuminate/container/BoundMethod.php:34
/home/ubuntu/api-key-dealer/vendor/illuminate/container/Container.php:576
/home/ubuntu/api-key-dealer/vendor/laravel/lumen-framework/src/Application.php:244
/home/ubuntu/api-key-dealer/vendor/laravel/lumen-framework/src/Application.php:229
/home/ubuntu/api-key-dealer/vendor/laravel/lumen-framework/src/Application.php:230
/home/ubuntu/api-key-dealer/vendor/laravel/lumen-framework/src/Testing/TestCase.php:62
/home/ubuntu/api-key-dealer/vendor/laravel/lumen-framework/src/Testing/TestCase.php:73

ERRORS!
Tests: 1, Assertions: 0, Errors: 1.
Script phpunit handling the tests event returned with error code 2

```

```
eval $(DEALER_HOST=localhost:8080./public/clients/algolia-keys-mac export)
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
-bash: declare: `-x': not a valid identifier
```

Start with the linked README documentation, then compare its `.env` and client-command instructions with the reported Ubuntu setup. Run `composer test` and inspect the `GenerationOfKeysTest::testTravisService` failure alongside the reported client command. Done means the setup instructions and command are clear and the documented test flow works; this issue has had no reply for years.

Written by the indexing model from the issue text.