nixops
nixpkgs
Our great sponsors
nixops | nixpkgs | |
---|---|---|
10 | 975 | |
1,716 | 15,656 | |
4.7% | 5.3% | |
6.5 | 10.0 | |
20 days ago | 5 days ago | |
Python | Nix | |
GNU Lesser General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nixops
-
20 Years of Nix
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
-
Will we move away from DSLs?
For example Nix can already replace ansible, packer, cloudformation[1], dockerfiles.
-
NixOS History and Our Experience - Nix, Null, Nada, Nothing
Nix can also ship the nixpkgs as an oci image (e.g. docker image), vm image, iso, or if you're able to: as a nixos configuration. Tools like nixops can allow you to deploy many machines and have their behavior exactly specified, and the configuration can be version controlled. NixOS configuration can be thought of as congruent configuration management, where many other tools give you many less guarantees about configuration drift and reproducibility.
-
The best solution for deploying flakes
There are 4 tools I'm taking into consideration right now, but every suggestion is welcome: 1. deploy-rs - I don't know anything about it, heard about it like a day or two ago 2. NixOps - the official one, I don't know what to think, but I have concerns about Flakes compatibility 3. morph - I understand this as "NixOps, but better", no more toughs. 4. colmena - seems to be pretty straightforward with quite nice docs
-
Spectrum OS: a declarative, reproducible, compartmentalized Linux
I'm still relatively new to NixOS, having switched all my personal systems over to it this spring/summer. I don't have a detailed answer to your question, 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/
-
Tool for managing multiple machines of a distributed system?
Nixops is specifically made for purposes like yours.
-
NixOS 21.05 Released!
Well, everyone of course! But especially devops, developers, power-users, and ricer folks. Due to the declarative and purity aspect of nixpkgs, all builds and configurations can be version controlled, cached and shared. NixOS can easily be extended to produce docker images, vm images, or even distributed deployments. You can also write reproducible multi-node integration tests. Tinkerers! Love playing around with the latest desktop manager or modifying builds? Nixpkgs allows you to modify any package you wish to, locally! Nixpkgs is actually a source distribution but its guarantees around purity and reproducibility are so strong that you can get a binary cache "for free".
-
Backblaze Is Now a Terraform Provider
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
-
Benefits/disadvantages of Guix System in general and over NixOS?
I'll have to read more about NixOps though, I had kind of forgotten that it existed!
-
NixOS Linux
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.
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
What are some alternatives?
deploy-rs - A simple multi-profile Nix-flake deploy tool.
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
git-lfs - Git extension for versioning large files
morph - NixOS deployment tool
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
nixos-generators - Collection of image builders [maintainer=@Lassulus]
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
patchelf - A small utility to modify the dynamic linker and RPATH of ELF executables
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.