nix
nixos-generators
Our great sponsors
nix | nixos-generators | |
---|---|---|
366 | 20 | |
10,621 | 1,439 | |
7.1% | 12.6% | |
10.0 | 8.3 | |
1 day ago | 3 days ago | |
C++ | 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.
nix
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Go + Hypermedia - A Learning Journey (Part 1)
1) Setting up the development environment - I currently use devcontainers for most things, but may also dig into nix -> isolated, portable, repeatable development environment 2) Exploring Echo - understand routing, requests, response, etc. 3) Incorporate Templ - integration with Echo, template composition, etc. 4) Integrating TailwindCSS - config for use with Echo/Templ, development cycle, deployment, etc. 5) Add in HTMX - endpoints, template structure, concepts, etc. 6) hyperscript for interactivity - client side interactivity
-
What it was like working for Gitlab
Semi-related, I would recommend to anyone who is a Linux native to try to find some kind of "minimum viable setup" that is really really easy for you to run out of VirtualBox or Parallels or something for this reason. No matter where you go, you know you can have a suite of tools which work just as you want them to there. Being able to tear it down and rebuild it quickly is also a great way to deal with debugging certain kinds of problems of the "it runs/doesn't run on my machine" category.
How you do this is of course up to you. At one end of the spectrum is just relying on your memory. At the other end is using NixOS https://nixos.org/ to get fully reproducible builds anywhere you go. Between these are a vast field of options. I know a guy who maintains an Ansible file set to `host: localhost` which installs everything he wants from that file. For me, I just stick with the latest Ubuntu version and maintain a few shell scripts [1] that install 80% of what I like to have on a new install.
If you like the scientific approach, you can install something like https://atuin.sh/ and do some statistics on what programs you actually run most frequently based on your long term shell history.
-
Cloudflare R2-Backed Nix Binary Cache on Fly.io
See https://github.com/NixOS/hydra/issues/838 for making content-addressed derivations supported by hydra.nixos.org. At that point, we can actually try out the XP feature at scale.
Also see https://github.com/NixOS/nix/issues/8919 for this accepted RFC
Once those things are done, we can get back to merging in the IPFS code.
Now that there is an Nix team and I am on it, there is much, much less of an issue of these experiments being caught in limbo :).
-
The one thing I do not like about the Nix package manager (and a fix for it)
The nix package manager is an awesome package manager for linux and macos, which focuses on declarative packages. This means that you can dump out all the packages you want into a file, and nix will go out and fetch them for you.
- NixOS: Declarative Builds and Deployments
-
Beginners Intro to Trunk Based Development
Secondly, our development environments must not drift, because then code may behave differently and a change could pass on our machine but fail in production. There are many tools for locking down environments, e.g nix, pkgx, asdf, containers, etc., and they all share the common goal of being able to lock down dependencies for an environment accurately and deterministically. And that needs to be enforced in our local workflow so we don't have to rely on CI environments for correctness. All developers must have environments that are effectively identical to what runs in CI (which itself should be representative of the production environment).
-
Practical Guide to Trunk Based Development
There are many ways this can be done (e.g nix, pkgx, asdf, containers, etc.), and we won’t get into which specific tools to use, because we'll instead cover the essential essence of preventing environment drift:
-
How I use Nix in my Elm projects
Nix is a tool that allows you to make reproducible development environments. I've started using it in all my Elm side projects and I've had a good experience with it thus far. To pique your curiosity I just wanted to share my simple setup that has been working quite well for me.
-
Shopware Changes since the 6.0 Dev Training Videos
The latter one is based on nix OS using Symfony flex recipes and PHP packagist composer. The flex devenv should work cross-platform on Linux, Windows, and Mac. "The main difference to other tools like Docker or a VM is that it neither uses containerization nor virtualization techniques. Instead, the services run natively on your machine."
nixos-generators
- NixOS-generators – Collection of VM and Container disk image builders for NixOS
- NixOS: Declarative Builds and Deployments
-
NixOS RFC 136 accepted: A plan to stabilize the new CLI and Flakes incrementally
Those Linode instructions are about installing an OS from an installation ISO from Linode's rescue mode. -- I'd consider that more a 'plus' to Linode that you get to be able to install whatever unsupported Linux on Linode's VMs. But, of course it's not as smooth as the officially supported images.
Sibling comment mentions that NixOS provides ways to build VM images (e.g. https://github.com/nix-community/nixos-generators has a generator specifically for Linode).
Another option is to use nixos-infect, which will replace a Linux distribution with a NixOS distribution. https://github.com/elitak/nixos-infect
> At that point, I feel like all of the repeatability gains are gone. If I want to spin up a fresh server, I have to read a guide and set stuff up by hand?
Just as with ansible, "git pull to deploy". You'd keep a copy of your NixOS configuration.nix somewhere else, and would be able to apply it later.
> it really does let me just get a new VPS and deploy to it very fast
Using a tool you're familiar with to get the job done is going to be faster than learning to use a tool you're unfamiliar with.
I believe much of the use of NixOS is for hobby stuff, and for personal machines. (c.f. "In what environments do you use Nix", Development (1242) vs Home Server (845) vs Production (386) https://discourse.nixos.org/t/2022-nix-survey-results/18983).
-
Couple of noob questions
If you need to generate lxc container in NixOS then perhaps this repo might be useful: https://github.com/nix-community/nixos-generators this article uses it https://www.thedroneely.com/posts/running-nixos-linux-containers/
-
disko-images - Create qcow2 images from NixOS + disko configuration
You might wanna check out nix-community/nixos-generators, it’s maintained by the same dude as Disko
-
How to do machine specific config on EC2 using an official nixos ami?
You can look at nixos-generators for support code that well let you take existing configs and build a variety of bootable images from them.
-
Flake to make NixOS iso
You should take a look at NixOS Generators, it's a flake with configs to build common formats like ISO, LXC, Docker, etc. I use that to generate an ISO with my config, specifically the packages.iso section.
-
Need help with NixOs VM Generation
I am trying to make use of https://github.com/nix-community/nixos-generators to generate qcow2 images from a NixOs configuration. Since it will be used with Scaleway, they require an efi bootable image.
-
Has anyone here spent a fair amount of time using NixOS/Guix and Fedora CoreOS/OpenSuse MicroOS for server deployment?
(2) There are a number of "generators" that can build disk images or installers. Some of them live in the nixpkgs repo along with NixOS, and others live in the nixos-generators repo. This is how I handle partitioning automatically. A related approach is to include first-boot scripts in those images. For example, the SD image resizes its main partition on first boot.
-
NixOS 21.05 Released
If you want to build custom images just use https://github.com/nix-community/nixos-generators
What are some alternatives?
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
void-packages - The Void source packages collection
flatpak - Linux application sandboxing and distribution framework
homebrew-emacs-plus - Emacs Plus formulae for the Homebrew package manager
guix - Read-only mirror of GNU Guix — pull requests are ignored, see https://guix.gnu.org/en/manual/en/guix.html#Submitting-Patches instead
NixOS-docker - DEPRECATED! Dockerfiles to package Nix in a minimal docker container
build-emacs-for-macos - Somewhat hacky script to automate building of Emac.app on macOS.
nix-darwin - nix modules for darwin
poetry2nix - Convert poetry projects to nix automagically [maintainer=@adisbladis]
devbox - Instant, easy, and predictable development environments