nixops

As far as I know, it’s still about [0]. I’ve had a better experience with deploy-rs though [1] - or even just using nixos-rebuild to target the remote machine. [0] - https://github.com/NixOS/nixops [1] - https://github.com/serokell/deploy-rs

I'm still relatively new to NixOS, having switched all my personal systems over to it this spring/summer. I don't do cloud dev atm, so haven't explored that use case yet. But I believe NixOPs is the canonical way to do what you're describing in production/at scale: https://github.com/NixOS/nixops https://nixos.org/nixops/manual/ (more below) If you want a more experienced answer, I suggest asking on the NixOS forum or subreddit, people are quick to answer in both places. https://discourse.nixos.org/ https://www.reddit.com/r/NixOS/ ---- More useful NixOPs guides https://www.thedroneely.com/posts/nixops-towards-the-final-f... https://ops.functionalalgebra.com/nixops-by-example/ https://nixops.readthedocs.io/en/latest/

> Even something that should be Nix's MAJOR selling point, like "create a single repo that configures a bunch of machines, including some NixOS and some other OS" doesn't have a recommended way to do it. NixOps[0]? But yeah, it isn't featured as prominently anymore as it used to be... [0]: https://github.com/NixOS/nixops

In addition to the other comments, there is also nixops. [1] [1] https://github.com/NixOS/nixops

You could use NixOps[0] for Nix but I'm not sure you can directly compare Terraform and Guix/Nix? My set up involves Terraform for infrastructure and Nix for provisioning, and it's working for me so far. [0] https://github.com/NixOS/nixops

Kind of off topic, but I would love to have NixOps (https://github.com/NixOS/nixops) as an abstraction layer for every type of cloud service, and not just virtual machines (e.g. queues, object storages, etc). There is Terraform and Ansible, of course, but Nix seems like it could combine the strengths of both of them.

https://github.com/NixOS/nixops NixOps is a tool for deploying to NixOS machines in a network or the cloud. Key features include: https://nixos.org NixOS is based on Nix, a purely functional package management system. by using Nix not only to build packages, but also things like configuration files. By building entire system configurations from a Nix expression, NixOS ensures that such configurations don’t overwrite each other, can be rolled back, and so on.

What advantages does Pyinfra have over NixOps? https://github.com/NixOS/nixops

There's NixOps: - https://github.com/NixOS/nixops - https://ops.functionalalgebra.com/nixops-by-example/

I think I might agree. I've been experimenting with making NixOps piggyback on terraform providers (https://github.com/NixOS/nixops/issues/1242#issuecomment-607...) in my spare time. I think this is the same mechanism as Pulumi uses now that I'm reading up on it. Perhaps I should create a Nix frontend for Pulumi instead... Interesting.

I would say Nix's cloud native story is "best in class". you can take any nixos configuration and turn it into a cloud image https://github.com/nix-community/nixos-generators You can take any nix package and turn it into a docker image https://news.ycombinator.com/item?id=20720922 https://news.ycombinator.com/item?id=18111954 You can even use Nix to create and deploy cloud resources ala Terraform: github.com/nixos/nixops Some other notable uses of Nix in cloud native landscape: https://github.com/saschagrunert/kubernix - a KIND alternative https://github.com/xtruder/kubenix a Nix DSL for defining and deploying entire kubernetes clusters + deployments (combines nix's docker image building support and deployment support for and end to end cloud-native solution) I personally think Nix should heavily market itself to the CLoud Native buzzwo

True, are you aware of the following Github issue related to this? https://github.com/NixOS/nixops/issues/565 It has links to solutions people are using, and other related issues.

FYI, there's a WIP PR for Vultr backend support in NixOps. https://github.com/NixOS/nixops/pull/634 I cherry-picked this into my local NixOps repo and have been using it for several weeks to deploy to Vultr servers with no issues, except one -- the author has hard-wired an assumption that you're using Btrfs for your root filesystem. I didn't want that so I simply replaced that hard-wired assumption with ext4 in my personal branch. Now everything is working great.

What it doesn't do: handling cpu quota on per "stack" basis, no builtin security isolation. That said, both use container technology for that. By solving the issue at a layer below (instead of adding one like docker does) it makes things much cleaner, more powerful making obselete puppet and the like. FWIW describing a containers/vm's/os'es in guix is much more easy than using docker. Have a look at https://github.com/NixOS/nixops too.