Troggle is the software which runs the the expo cave survey data management and website.
For earlier history see Website history.
Covid lockdown has been good to troggle. During March and April Philip migrated troggle up to Django 2.2.19, excising the ancient and unused user registration system on the way. Django 2.2 LTS is a long-term stable relase which will be in-support by Django until April next year. Wookey discovered and ran the Django system testsuite on the Debian server thus enabling us to use a necessary (but obstensibly outdated) link between Django and the database MariaDB. As of April 9th troggle is now running on software which is actually 'in date'.
We plan to stick with this configuration for a year.
On 15th March Wookey upgraded the server to the debian release 11 bullseye. At this point 'debian stable' is bullseye and has python 3.9 as standard. We will quickly migrate to Django 3.2 LTS which is now a year old and which will be supported until April 2024. Bullseye will be in support until June 2026.
Django migrations are not nearly as painful as they used to be, and troggle is already compatible with Django 4.0.3 (though we won't use that). So the presure to migrate from Django is now very greatly lessened. However, see troggle architecture speculations and possible migration from Django.
We should not need to anything until we move from Django 3.2 LTS to 4.2 LTS before April 2024.
Wookey at last, after much effort, got the loser repository converted from mercurial to git, with much tidying and history-reconfabulation. He says this will need to be done again, but it was good enough for the 2022 Expo. Also the troggle code was changed: survex files edited on a webpage now automatically commit to git with no user involvement.
Just before expo, we finished integrating the formerly-separate 'wallets' script. So now the progress of scanning and tunneling survey data can be managed more easily. This has turned out to be unexpectedly powerful. And it works on the data back to 1999 too.