aconfmgr VS nix-helpers

Establishing a backup strategy. I'm using BTRFS with snapper and a pacman hook that creates a new snapshot before each upgrade. With ext4 I used timeshift. Besides that, I save my arch configuration with aconfmgr and my files with borg

Since my last cloning I've setup aconfmgr and and systemd-homed. I've also been playing around with archinstall configs to partition the system with encryption how I like. In the future I'm planning to use archinstall and aconfmgr to setup a new system for me and then I'll copy over the backup of my home directory.

try this https://github.com/CyberShadow/aconfmgr

Have you tried aconfmgr? In addition to installing packages, it also tracks configurations in /etc and modified files.

For my backup I keep files in my home directory synced with my NAS via syncthing. For my system backup I don't actually backup up my system, I configure my system via aconfmgr and that config is stored in my home directory and synced to my NAS. Using aconfmgr to "backup" my system is extremely space effecient, my aconfmgr config is only 1.7 MB.

aconfmgr (in AUR) can be used to save and restore system configurations and installed packages. For user configuration you can use a dotfile manager like chezmoi (in repo).

I know you prefer backing up manually, but aconfmgr might be for you.

To get something closer to nix on arch I like to use aconfmgr.

For those who are not familiar with Arch's aconfmgr, well I have not used it before but just saw it in a post. But it seems to be a configuration manager for Arch. It tracks, manages, and restores your Arch Linux OS configuration.

Yes, to get Nixpkgs it's much faster to use `fetchTarball`.

You're right that `builtins.fetchTarball` is faster than `builtins.fetchGit` (due to the ridiculous amount of commits in the Nixpkgs repo). I like to keep such definitions in a single, company-wide/project-agnostic git repo (what the Nix Pills series calls the "repository pattern"), and have individual projects import them via `builtins.fetchGit`.

Many years ago we didn't have `builtins.fetchGit`, so had to use the 'fetchgit' function from Nixpkgs instead. That created a chicken-and-egg situation if we wanted to take the Nixpkgs version from some other git repo; hence needing to "bootstrap" via `(import { config = {}; }).fetchgit`, and cross our fingers that `NIX_PATH` wasn't set to some crazy value (which, of course, I would inevitably do... https://github.com/Warbo/haskell-te/blob/24475a229908caa3447... )

Note that we need `config = {};` when importing Nixpkgs to avoid an impurity which tries to read files in $HOME. More recent versions of Nixpkgs also need `overlays = [];` to avoid another impurity (looks like this changed at Nixpkgs 17.03, according to https://github.com/Warbo/nix-helpers/blob/master/nixpkgs.nix )

Where nixpkgs2105 is a pinned revision of the Nixpkgs repo, defined in another overlay. My current Nix config has pinned Nixpkgs versions going back to 2016. For example, here's a bunch of such overrides:

https://github.com/Warbo/nix-config/blob/master/overrides/fi...

At the moment I'm using niv to manage the pinned Nixpkgs versions (the 'repoXXXX' entries):

https://github.com/Warbo/nix-helpers/blob/master/nix/sources...