March, 7, 2024 archives

One of the benefits of starting Frozen Soup from a project template is that someone very smart (Simon) has done all the heavy lifting to make publishing it into the Python ecosystem really easy to do. So after I added a new feature today (pulling in external url(...) references in CSS inline as data: URLs), I went ahead and registered the project on PyPI, tagged the release on GitHub, and let the GitHub Actions that were part of the project template do the work of publishing the release. It worked on the first try, which is lovely.

I pushed more changes after I did that release, adding a way to set timeouts and fixing the first issue (that I also filed) about pre-existing data: URLs getting mangled. I also added a quick-and-dirty server version which allows for getting the single-file HTML version of a page, and makes it a little easier to play around with the single-file version of live URLs without having to deal with saving and opening the files.

So I did a second release.

For some reason I couldn’t keep the the instances I was setting up on Oracle Cloud Infrastructure (OCI) from eating themselves when I did something fancy like run apt-get update, so I moved everything back to Linode ($100 referral credit there) on one of the lowest-price Nanode compute instances.

I took the opportunity to rebuild the host on Debian just to give that a spin. My setup runs on containers managed by docker-compose, so the underlying system doesn’t matter to me that much.

I should probably be using this as an opportunity to learn some infrastructure-as-code tools.