Is it safe to update mongod* packages outside the script (directly with apt)? I prefer to leave security updates (and only those) to unattended upgrades, but it doesn’t cover these since they’re from the mongodb repository. AFAICT, the script would only allow me to update all packages (with ”Update the Operating System”), but I don’t want non-security updates.

mongod-amd64/noble 8.0.8 amd64 [upgradable from: 8.0.4]
mongodb-database-tools/noble/mongodb-org/8.0 100.12.0 amd64 [upgradable from: 100.10.0]
mongodb-mongosh-shared-openssl3/noble/mongodb-org/8.0 2.5.0 amd64 [upgradable from: 2.4.2]
mongodb-org-database-tools-extra/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]
mongodb-org-shell/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]
mongodb-org-tools/noble/mongodb-org/8.0 8.0.8 amd64 [upgradable from: 8.0.5]

Yes, the qemu solution seems simpler and more future-proof than the custom Unifi repository.

Also, my guess would be that few people running Wekan on hardware old enough not to have AVX will have a massively large user base on their installation; most are probably small-time hobbyists like myself, so any negligible slowdowns being exacerbated by scale won’t be much of an issue.

I can already guess the answer to this is ”no, because of how snap works”, but would it be possible for Wekan (installed as a snap) to use mongodb tools already installed on the host system? The reason I’m asking is that I’m running Unifi’s network application on the same non-AVX-capable host, and the installation script for it has added a mongodb repository patched to work without AVX, so that’s already covered.