nix-installer VS nix

This is a way improved[1] version of the official installer, capable of uninstallation among many other things, there is no need to use the official one: https://determinate.systems/posts/determinate-nix-installer

1: https://github.com/DeterminateSystems/nix-installer?tab=read...

The Determinate Systems nix installer is quite smooth: https://github.com/DeterminateSystems/nix-installer/

Though it does tend to get clobbered on macOS updates.

and that's just the simple version, on Linux, and thus is likely the happy-path in CI.

When trying to use it locally on macOS, this here is just some "you wanna do _what_?!": https://github.com/DeterminateSystems/nix-installer/tree/v0.... (not to pick on determinate.systems, the upstream is similarly facepalm: https://nixos.org/manual/nix/stable/installation/installing-... )

I installed nix with the following nix-installer: bash curl --proto '=https' --tlsv1.2 -sSf -L https://install.determinate.systems/nix | sh -s -- install Now I'm trying to install home-manager and I'm starting from 3.2 Standalone setup with the following command: bash nix run home-manager/master -- init --switch but it gives me the following error message: Could not find suitable profile directory, tried /home/tornax/.local/state/home-manager/profiles and /nix/var/nix/profiles/per-user/tornax

Alternatively the Determinate Systems Nix installer runs on Steamdeck. They even have instructions for setting up a Steamdeck VM where you can try out anything before buying (other than running games).

Nice write up. But my question would be why not just use the Determinate Systems Nix installer to install nix? Is there a specific reason you went with Guix?

Personally, I like using this alternate installer. I find it a bit easier to work with. https://github.com/DeterminateSystems/nix-installer

You should be able to install both in a container and on the host. And for the install script, no idea why it doesn't work for you, but there's also an unofficial installer you could try: https://github.com/DeterminateSystems/nix-installer

I've installed Nix on macOS using nix-installer. Now I can start a temporary nix shell using nix-shell -p git direnv as an example, but I need both of these packages "globally" outside of a nix-shell. How do I do this on macos?

> https://github.com/NixOS/nix/pull/9911#issuecomment-19252073...

As we covered in my last post, NixOS is a amazing Linux distribution for creating stable and declared environments. Now while this is amazing for a desktop setup, it is also perfect for a home-server or home-lab.

(Nix itself is slowly chugging along with Windows via MinGW - https://discourse.nixos.org/t/nix-on-windows/1113/108 and https://github.com/NixOS/nix/issues/1320 , for example.)

Nix is a cross-platform package manager. It uses the nix programming language. Nix and NixOs are often used in the same context, but while the first is a package manager, the latter is a linux distribution based on nix.

Today I want to talk to you about Nixos. What is it? Nixos is a declarative and reproducible OS, partly taking the words used on their own page. What does that mean?

Software developers often want to customize:

1. their home environments: for packages (some reach for brew on MacOS) and configurations (dotfiles, and some reach for stow).

2. their development shells: for build dependencies (compilers, SDKs, libraries), tools (LSP, linters, formatters, debuggers), and services (runtime, database). Some reach for devcontainers here.

3. or even their operating systems: for development, for CI, for deployment, or for personal use.

Nix provision all of the above in the same language, with Nixpkgs, NixOS, home-manager, and devShells such as https://devenv.sh/. What's more, Nix is (https://nixos.org/):

- reproducible: what works on your dev machine also works in CI in prod,

- declarative: you version control and review your configurations and infrastructure as code, at a reasonable level of abstraction,

- reliable: all changes are atomic with easy roll back.

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.

- it reduces bloat, because you can generate an environment or OS image with only the software needed to run a specific program or service

My guess is that a big efficiency gain would come from the second point, because you don't waste CPU on code that you don't use.

Does this make sense? Has anyone explored this?

[0]: https://nixos.org

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