POCO VS Home Manager using Nix

You can also look into Poco https://pocoproject.org/

I can't say enough good stuff about POCO for this type of work - when I first got my teams using it we used to joke that POCO was what Boost wants to be when it grows up. And nlohmann/json - cracking library for working with JSON in C++.

We use https://github.com/pocoproject/poco in most projects, very easy to set up a http listener

Did someone used Poco's Net Library to create a Rest Api? Poco Project

But CLion is so slow. Tested with Poco C++ standard build (https://pocoproject.org/). Moving around with Go To Definition takes sometimes up to 20 seconds if file is first touched. Using 'back' and 'forward' delays for 1-2 seconds.

Yes, you need NetSSL - take a look at find_package(Poco REQUIRED COMPONENTS ... NetSSL) requires an aditional find_package(OpenSSL) since poco-10.

poco (portable components) https://pocoproject.org/

To have your Nix-based setup reproducible across different OS (Arch, Debian, Ubuntu, WSL2, MacOS, and NixOS), and have an extensible base config that can be customized to different situations, the go-to framework is home-manager (not NixOS, which only works on NixOS, or NixOS on WSL 2).

https://github.com/nix-community/home-manager

Just NixOS. When building the VM / live CD I copy my dotfiles into the Nix store and then during first boot-up I copy them into my home dir and set up symlinks.

The main reason I decided against home-manager was that it makes my simple symlink setup (~/.foo -> ~/.dotfiles/foo) virtually impossible: Symlinks will always point to the read-only Nix store in one way or another. See https://github.com/nix-community/home-manager/issues/3514 or one of the countless other tickets on the topic. Through this episode I also learned that home-manager isn't exactly well-documented, either, and also quite opinionated. (Which, to be fair, is not a bad thing – if it works for you, it probably works great.)

Finally, not using home-manager was also a risk management decision in that it's probably best to not go all-in on Nix, NixOS, home-manager etc. all at once. Start with the simplest possible config that gets you running, then iterate.

(Declarative rclone https://github.com/nix-community/home-manager/pull/6101)

Atop all this is the Nix Operating System, or NixOS. NixOS brings all of the declarative goodness of Nix into a Linux distribution. This means that (almost) everything about your system is declarative, including the packages (obviously), the users, the desktop, the login manager, systemd units, containers, and among other things, even the bootloader! Through some extensions, you can also partition disks, build images, and even configure your home folder. A single NixOS configuration is built into multiple pre-configured operating systems using just a single command!

Read more at: https://github.com/nix-community/home-manager

While I don't use NixOS or home-manager, I would imagine this provides some extra value: i.e. config is versioned or easy to move between machines.

Curiosity got the better of me so I looked it up at https://nix-community.github.io/home-manager/ and it indeed does purport to provide benefits I guessed at and then some.

Whether that's better than just manually managing things yourself is altogether a different matter.

Nix Home Manager is a tool for managing a user environment with Nix. It already has a nice way to install and configure gh with the programs.gh option:

The data definition and operational model of SOPS is well suited for a Nix-powered system. sops-nix offers both NixOS and Nix Home Manager modules which provide a declarative way to manage secrets using SOPS.

There is also nix-on-droid[1] which is a fork of Termux allowing you to manage your environment with nix (similar to home-manager[2])

[1]: https://github.com/nix-community/nix-on-droid

[2]: https://github.com/nix-community/home-manager