It doesn’t need to be fully automatic, can rely on human intelligence. Let’s say it is called install app, and you are supposed to run it just once in the target computer, and it can even take an argument with the destination. Will that bee too far away from your project objectives?
Maybe it’d be help if you can show a use case, I currently don’t see the value of saving a simple git clone command.
I have published my personal configurations here: GitHub - hgl/configs: My nix configurations
It’s pretty simple to bootstrap.
I also added a few more examples to Quick Start (check the GitHub repo page).
I imagine terraform modules like nixos-anywhere’s may also handle parallel deployment
Unfortunately it doesn’t, and nixos-anwhere does installation, not deployment. Nixverse does use nixes-anywhere under the hood and can provide parallel installation on top of that. But parallel installation is probably niche comparing to parallel deployment.
1 Like
nixos-anwhere does installation, not deployment
could it be you’re speaking from experience with their CLI, rather than with their terraform module?
My mistake. I was not aware of its terraform module. Very cool that nixes-anywhere can do that.
A shameless plug: it might also be helpful to point out that Nixverse is more than a deployment tool. Its group feature allows you to define your ssh public keys in one place, and have all its descendants automatically accept them, for example.