Document all config settings and functional/technical specifics for "Batch test mode"

[baknu]

Document all config settings and functional/technical specifics for "Batch test mode" (i.e. differences compared to "Single test mode"), like:

• Rest API
• User authentication
• Only website test and e-mail test
• No connection test (so also no DNS records for this test. Also see: https://github.com/internetstandards/Internet.nl/blob/main/documentation/Docker-deployment.md#dns-setup)
• Only web page with test results available for authenticated user, no tests possible via web interface
• No prechecks **
• No WHOIS info
• No HoF
• Longer caching of test results for reuse when the same domain is tested in a given time?
• Availability period of API results
• CENTRAL_UNBOUND?
• Additional DB indexes?
• No rate limiting of a single IP using Internet.nl? (Note that this is done in "Single test mode".)
• Include all info that is now made available via https://github.com/internetstandards/Internet.nl-API-docs/blob/main/v2.0/API-v20-documentation.md
• … ?

The current documention on https://github.com/internetstandards/Internet.nl/blob/main/documentation/Batch.md does not seem to be up-to-date and complete.

---

** Mail from GT to DB and BK on 21th of June 2019:

For the current batch release I tried to enable the DNS prechecks we also have in the internet.nl UI. They were not implemented in the batch environment because they introduced latency in the initial design. I tried to enable them with this release but the overhead is still not acceptable for long lists of domains as DB found out when he was trying to test > 10K domains.

[mxsasha]

* Only web page with test results available for authenticated user, no tests possible via web interface

This isn't actually true though? I can launch a test from https://batch.internet.nl/ if I have a valid login. I actually find this very useful for checking on issues.

* Longer caching of test results for reuse when the same domain is tested in a given time?

This does not happen as far as I can find in the code.

* Availability period of API results

We have nothing configured for this.

* CENTRAL_UNBOUND?

I believe we dropped this.