I want to learn how to do more devops and I love Nix, so I have a new project I want to work on: automatic deployment of a website from a merged pull request, all using Nix.
I'm finding myself getting sidetracked by describing what Nix, NixOS, and Nixops are, so I'm just going to assume you've done all of the relevant reading on what those are. In short, Nix is a tool for building programs (and, perhaps a bit too confusingly, the language that build instructions are written in), NixOS is a Linux system fully administered using Nix language instructions, and Nixops is an environment deployment program for building and deploying NixOS systems to various targets like AWS or VMs. I already use all three to run my own private websites, but it's a rather manual process for getting updates deployed.
The current process is:
I notice the need for a change (maybe a spelling mistake)
I make a change to the source code, commit it, and push it to Github.
I note the new commit (or tag a new version number) and change the instructions in nixops.
I run a test build so that the shasum check against the new Github commit hash fails (I'm lazy, I know I could pre-hash this earlier but it's just easier to copy-paste it from the failed build log).
I tell nixops to deploy the new system.
The process I want to get to:
I notice the need for a change (maybe a spelling mistake)
I make a change to the source code, commit it, and push it to Github.
Since I'm ready to deploy I tag a new version number (or maybe make a merge request to merge it into a “release” branch, still not sure what the best way to go about this is).
Nothing, because I want the rest of this process to be fully automated.
I know it may not be easy or even possible. It might be that I'll still need to manually update the version number and hash in some Nixops code. Nix is rather particular about no-exception enforcement of shasum checking of source code, and probably for good reason. If I can't have the system automatically deploy from a change in the source code, I want to automatically deploy from a change to the Nixops source code repo. We'll see.
Anyways, that's my goal and I hope to write another blog detailing my success or failure.
Sons of Michael, he approaches!
Rise; the Eternal Father greet:
Bow ye thousands, low before him;
Minister before his feet;
Hail the Patriarch’s glad reign
Spreading over sea and main.
Sons of Michael, ‘tis his chariot
Rolls its burning wheels along!
Raise aloft your voices million
In a torrent power of song;
Hail our Head with music soft!
Raise week melodies aloft!
Mother of our generations,
Glorious by Great Michael’s side,
Take thy children’s adoration;
Endless with thy Lord preside;
Lo, to greet thee now advance
Thousands in the glorious dance!
Raise a chorus, sons of Michael,
Like old Ocean’s roaring swell,
Till the mighty acclamation
Through rebounding space doth tell
That the Ancient One may reign
In his Paradise again!
Just a bit of Adam-God completely normal Mormon poetry for today. This is still in the LDS hymnal (slightly altered, of course)!
Hello, fediverse
Now you can follow this blog from Mastodon and other federated platforms! Just search for @blog@blog.nocoolnametom.com to start getting my posts.
No, wait, hear me out! The older manuals spent time detailing exactly what the teacher should go over. It spelled out what scriptural passages to cover, offered possible questions that could be asked to the class, and offered many explanatory sections to help the teacher present the scriptural texts with at least some historical context. They were restrictive and constraining, and, as I've detailed in my explorations linked above, they often presented outdated or even incorrect information. That's all admittedly pretty bad, so why do I think the new ones are worse?
Because while they have (thankfully) gotten rid of the specified verses that should be read (which produced a patchwork of biblical literacy for most Mormons featuring large gaping holes), they have totally removed nearly all of the historical context. The entire aim is now to merely play the old “Apply This To Yourself” game with Every.Single.Passage.
This is the game that goes, “I don't really understand this, but the general gist makes sense to me. And it reminds me of that time in my life when I [fill in the blank], so I guess it's about that.” It's both a recipe for producing a wonderful connection with the Biblical text as well as a recipe for producing terrifyingly incorrect assumptions of the meaning of a two-thousand-year-old library. (There is nothing in w