5. ESI Fetch configuration and cron job
In ACP -> SSO Keys, there are a few preferences you can set.
- Maximum processing time per ESI SSO key [s]:
This setting restricts the amount of time EDK may spend processing kills for a single SSO key. This is useful if you cannot influence the maximum execution time of your PHP installation, to make sure that each registered SSO key is processed.
- Ignore NPC only deaths?
Like with the old API import, you can choose whether deaths to NPCs should not be imported.
- Only allow board owners to register?
If this setting is enabled, only characters that are member of the alliances or corporations who are configured as board owners are allowed to register. If specific pilots are configured as board owners, only these pilots can register for ESI kill fetching.
As a replacement for the old cron_api.php CronJob, a new CronJob cron_esi.php was added. The recommended execution frequency is every five minutes.
For each SSO key, ESI Fetch will start fetching from the first killmails available up until it reaches the present. So it might take quite some time until you'll see current killmails on your killboard. Setting the appropriate cronjob to be executed every 5 minutes will speed up the process.
Enabling debug for ESI:
The ESI client library supports debug logging for all requests/replies sent to/received from ESI, including the response times. To enable debug logging, add the following line to your kbconfig.php file in your killboard's root directory:
The ESI debug.log file will be create in the cache/esi folder.