Gitops

The default for Forgejo is to use local storage but I wanted to migrate to Linode (Referral ) Object Storage for better scaling since I am using a lower spec VM for my instance. I found the post Upgrading Forgejo with S3 Object Storage which gave me a good starting point.

I was surprised when reading the changelog for Salt 3007.0 , regarding several deprecated modules to be removed in 3009.0. I also later read some of the policy changes on their blog. Going forward, they are planning on having a much smaller core module, and will be moving a lot of larger modules to external repositories.

I started using Salt while I was at Kotagent, and quite liked the way it worked. Even though a lot of teams at my current company use Ansible, I never enjoyed using it, and somewhat forced my team to switch to Salt (this was easy because my team was mostly just me). I think Salt tried to include too much into its core, and over time it feels like the increase maintenance burden resulted in a product that moves slow and was hard to improve. I hope having a cleaner core, and moving a lot of modules out will result in being able to have a more reliable core, while keeping it easy to extend via the various types of modules.

I’ve used Namecheap for many years for hosting my DNS. It’s nothing particularly special but it works well enough for my needs. When managing DNS entries it can sometimes be a little annoying doing everything on their web page. I’d rather be able to script something. After thinking about it for a while, I finally created something.

Namecheap’s API is implemented in XML which makes parts of it feel a bit old, but our use case is fairly simple. We can use get-hosts to download a backup of our DNS entries for history, and then set-hosts to publish our new values. I wrote a class to handle the basic Namecheap API calls (which is mostly formatting them and wrapping the requests library).