NixOS-WSL
nix-cue
NixOS-WSL | nix-cue | |
---|---|---|
6 | 1 | |
1,463 | 25 | |
7.6% | - | |
9.0 | 0.0 | |
8 days ago | almost 2 years ago | |
Nix | Nix | |
Apache License 2.0 | 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.
NixOS-WSL
-
NixOS for the Impatient
I have not used it but this might be what you are looking for: https://github.com/nix-community/NixOS-WSL
You could also install the nix package manager on Ubuntu.
- NixOS VM on windows machine
-
Easy and reproducible WSL distributions, with home-manager and Alpine linux
This project began as I didn't like that NixOS-WSL used systemd in the background, so I made this for myself. Some of the advantages: faster boot time, smaller image size and a FHS distro in the background, that lets you load dynamically linked binaries (for example, to have VSCode remote working OOTB).
-
About using Nix in my development workflow
There's a community port of NixOS to WSL2, complete with systemd support, plus Docker Desktop support and some other goodies: https://github.com/nix-community/NixOS-WSL
Nix also works on other WSL distros, provided they're using WSL2.
Nix supports cross-compiling Windows binaries as well. I know some people use it for that.
There is no 'native' support— you can't use Nix as an alternative to Winget or Chocolatey on Windows. Right now a lot of important stuff in Nixpkgs depends on a POSIX shell and Unix coreutils implementation for the basic build environment, and that's shared between many operating systems. Trying to fit Windows into that doesn't really make s sense, and there's not really any momentum behind the idea of using any particular other runtime environment (could be a scripting language instead of a shell + coreutils) for those basic builders.
But it's conceivable that some day, one or more companies using Nix on WSL might see vaiue in taking that extra step and put together a Nix-based package collection for Windows and help get the Nix Windows port out the door.
-
Build a temporary package to get started, iron out deps and learn how things work...
Basically, I managed to get NixOS inside WSL2 by using this: https://github.com/Trundle/NixOS-WSL
-
does nixos-wsl work in vscode with the wsl extension:
But whenever I try running code . with nixos-wsl(https://github.com/Trundle/NixOS-WSL), the error: `code: command not found` is thrown, also, whenever I try to open nixos-wsl from vscode, it does not work and the terminal throws a bunch of errors?
nix-cue
-
About using Nix in my development workflow
You're basically right. I'm not 100% sold on this idea, but I think it's a possibility. Most of what I'm seeing right now is CUE facing outward, e.g., to generate typed things from within nix. This[1] is a good example of that. Given how flexible CUE is, and given how similar nix is to HCL, I think it's possible to have CUE emit nix and provide some basic typing that way.
[1] https://github.com/jmgilman/nix-cue
What are some alternatives?
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
nixago - Generate configuration files using Nix [maintainer=@jmgilman]
dotfiles - :wrench: .files, including ~/.macos — sensible hacker defaults for macOS
bitte - Nix Ops for Terraform, Consul, Vault, Nomad
nixos-vscode-server - Visual Studio Code Server support in NixOS
direnv-nix-lorelei - Alternative Nix extension of Direnv
nixpkgs - Nix Packages collection & NixOS
nix-direnv - A fast, persistent use_nix/use_flake implementation for direnv [maintainer=@Mic92 / @bbenne10]
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
digga - A flake utility library to craft shell-, home-, and hosts- environments.