There's going to be some work we need to do for Acrarium:

• Use Ankidroid's own DO account for hosting the droplet.
  • Who pays for this? @mikehardy willing to use personal billing info, but AnkiDroid pays via reimbursement from OpenCollective
  • Consider upgrading to a droplet with better specs (more cores&RAM) so that it's actually usable.
  • Who should we have maintaining the droplet? Do we need more than one person?
• Upgrade to Acrarium 2.
  • Not even released yet? About 300 commits since the latest stable release: F43nd1r/Acrarium@v1.8.1...v2.0.0-beta09
  • I found several dependencies in the beta with fairly high CVE scores and pinned the patched versions to fix this. Not sure how bad stable looks. Should consider submitting a PR with my changes.
  • Purge old reports in a cron job or something. Problem: Acrarium's API endpoint for reports does not support delete operations. Maybe we can just.. drop records from the database directly?
  • Problem: I tried upgrading to the latest beta with the current database as-is, but Acrarium got stuck during the database migration saying something like "duplicate column name". I tried tinkering with the MySQL dialect variable as mentioned here to no avail. Idea: Dump a (very) small proportion of our DB and try migrating it, instead of doing the whole DB at once, so that it becomes faster to debug any migration issues by changing settings around and so on.
  • Try adding Proguard mappings, again? Didn't work for me on the droplet (Acrarium v1.8.1). Trying to open any report results in an "Error 500" page. Good to know: After a few "Error 500" messages, you can get back into the admin panel and upload an empty mappings file for the app version that's now bugged out. That has always un-bugged it for me, so that I can check reports for that version.
  • Check to see if filtering has changed in Acrarium (maybe it has improved?). I have personally felt that it is a bit lacking, like when trying to filter after a specific field in the reports.
  • Check if ingress stack matching is possible with the newer version, without degradation of performance on the droplet (or total meltdown, apparently?) Mike has way better knowledge about this.