To add onto this, I have been using Libreoffice Online or Collabora Online for the last 4 years or so. I used to compile LOOL myself but eventually I just switched over to using the Collabora Online Development Edition that Collabora releases. I am using it integrated with Nextcloud.
I enjoy using it and it has been a life savior for the times I need to work on a document with someone else since I can just send them a share link for it. The fact that it uses leaflet which is meant for maps does mean that the latency to the server matters quite a lot to experience but I don't mind that much, personally, with my not great 120ms RTT to my server.
A change in your repo does not need to result in an import path change if you set up vanity URLs for your import path. For instance, all my go libraries use the import path of gomod.garykim.dev even though the repos are actually hosted on GitHub. That means if I ever change to self-hosting, for example, I just need to update some of the meta tags on the gomod.garykim.dev website to change the repo location.
I don't know how I would live without that. I tend to make rather verbose branch names and typing it all out stuff like push would take forever.
Though, you have a much more fun solution.