# NixOS shines here as well because all the upgrade related changes are handled by the NixOS service code written and tested by expert maintainers, instead of random admins like me. The # Mastodon upgrade went without a hitch, as have all previous ones. The isolation and reproducibility (and composability) is worth learning the complex # Nix language. So, the point I'm trying to make here is, use NixOS for setting up your servers. But no problem, I just ran the build again, and everything was back to how it was. I also managed to wipe out the whole Nix store while trying to figure out the Bookwrym build issue (by running garbage collection). So I just copied the previously working channel for Bookwyrm and changed its config to use the same, upgrading only Mastodon.ĭoing these kind of things would be so cumbersome if I had not been using NixOS. Mastodon upgrade worked fine but Bookwyrm refused to build because of some Python packaging issues. While trying to upgrade fantastic.earth to # Mastodon 4.2.1 today, I accidentally ended up upgrading the # Bookwyrm service as well because both of them were using the same # NixOS pinned channel.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |