Move service configurations and deployment state, including user data, from one hosting provider to another.
nixops4 apply
Pretty good, awesome that it's all green now! Let's merge it like that, and keep cleaning it up. It's still a bit too hard to follow for my taste, because some unnecessary abstraction obscures the actual test cases. Ideally test cases would contain pretty much a (simplified) deployment as one would actually write it for production, and next to it a script that interacts with it to check invariants.
nixops4 apply
This looks pretty good from afar, but I'd like to take another full pass and then merge.
nixops4 apply
deploying some services through the panel, and...
Right, we can also have these two in sequence, because once we have a from-source bootstap we can cheaply produce images.
We can always build a base image with Nix (and we do), the question is more what the user/hosting-provider experience is supposed to be. I think the issue description as is should be more like a…
This is blocked on Fediversity/Fediversity#277 to verify that we're not breaking what we already had working.
This is blocked on an integration test verifying that the deployment indeed works.
This is blocked on (re-)defining OKRs, but this is a team effort that requires all stakeholders.