Operations for upgrading batch to Docker

[baknu]

1. • [x] Deploy on dev-docker.batch
2. • [x] Add users + credentials (BATCH_AUTH); See: https://github.com/internetstandards/Internet.nl/blob/main/documentation/Docker-deployment-batch.md#application-setup
3. • [x] Check and fix documentation: https://github.com/internetstandards/Internet.nl/issues/1201
4. • [x] Point acc.dashboard to dev-docker.batch
5. • [x] Comparison test (1. dev-docker.batch vs. batch and 2. dev-docker.batch vs. dev-docker)
6. • [x] Load test (for reference in 2023 the peak was 91,493 tests per day (66,471 email tests and 25,022 website tests))
7. • [x] Set up new batch-docker server Make sure these are fixed:

     • 1258

     • 1274

     • 1275

     • 1267

8. • [x] Revisit and document INTERNETNL_CACHE_TTL, cache-max-ttl and cache-max-negative-ttl (see mail from BK dd 2 April 2024)
9. • [x] Setup batch-docker in DNS
10. • [ ] Copy over user list.
11. • [ ] Deploy on batch-docker + import database (from batch-prod/old)
12. • [ ] IP switch between batch-prod/old and batch-docker like on single
13. • [ ] Power down batch-prod/old
14. • [ ] Drop -docker labels from everything in DNS

[mxsasha]

Should we do another comparison of current batch production (1.7) to dev-docker.batch (1.8)? I think we're just going to re-find all known 1.7 and 1.8 differences. I do see added value in dev-docker vs dev-docker-batch, as it reveals whether batch mode introduces any new issues currently not known.

[mxsasha]

Comparison test done, no unusual differences.