aconfmgr VS nix-prisma-example

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.

For the system, I like the devos template:

https://github.com/divnix/devos

The idea of flakes is how you define inputs, and you define the system (and packages, and shell etc.) in the outputs using the inputs. The inputs are git repos which point to other flakes. You can mix and match these as much as you want (see the devos repo for examples) and when you build the derivation, it generates a lockfile for exact commits in that point in time what were used in the given inputs.

You commit the lockfile and in the other systems where you pull your config from the repo, it uses exactly those commits and installs the same versions as you did in your other systems.

This was quite annoying and hard to do before flakes. Now it's easy.

The problem what people face with building their system as a flake is combining the packages so you can point to `jq` from the unstable nixos and firefox from the stable train. I think this aspect needs better documentation so it wouldn't be so damn hard to learn (believe me, I know). Luckily there are projects like devos that give a nice template for people to play with (with documentation!)

Another use for flakes is to create a development shell for your repo, an example what I did a while ago:

https://github.com/pimeys/nix-prisma-example

Either have `nix-direnv` installed, enter the directory and say `direnv allow`, or just `nix develop` and it will gather, compile and install the correct versions of packages to your shell. Updating the packages? Call `nix flake update` in the directory, commit the lockfile and everybody else gets the new versions to their shell.