Grand rewrite: Rewriting the web client from Django to Go

I just noticed that the new Go UI as been in development since 2016...

Yup... that's when I had already identified the risk from Python and Django being unsupported and realised I needed to get started. I'm glad I did, the vast majority of the foundation was laid back then... i.e. everything about templating, the API, the authentication, the caching... all the big things I poured time into. Then I got demotivated by the sheer amount of work remaining, and my full-time work became ridiculously demanding and going into burn-out zone.

Are you doing some load-balancer magic and serving the UI from both projects at the same time? Slowly migrating endpoints across?

Nope... I intend to get the majority of the user path done and then to switch a single website (this one) to use the new frontend and to find issues and fix them. When it's basically there, then I intend to switch all of the others over.

I could do a complex thing... i.e. "read only version of that page goes to the Go backend, all other versions go to the Django backend"... but it would be very hard. Mostly because I've shifted the new stuff to use a cryptographically secure cookie and that isn't implemented in the Django side. Same for CSRF tokens, etc... the read only and write parts of the site have to be served by the same app. So I have no intention of maintaining that in any way that would support a mixed-platform migration.