move standalone home-manager users into their associated host directories
move packages from packages.nix files kept with user directories to modules with
namespace groupings
custom options: enable and package to use
create role directories to house system and home modules for given host role with associated config
eg. have a workstation role that enables all packages I want on every workstation through my custom modules
add options to existing modules and to be created package housing modules to account for possible difference per device
eg. add a custom config option to my hyprland module which takes a path to a config to import stored in the given host with hyprland config specific to that device (think monitors and possibly some window rules)
The above will move my config approach from reusing users per differing host to reusing modules which is better practice and better organize my packages on enabling making readability very nice. This does result in more code than if I just created a new packages.nix file for each new user which I could create on demand but this feels better. Also, I am interested in how this turns out.
Generally each workstation device will have 95 to 99% the same config but I want to handle that small percent nicely and copy nicely readable custom module enable code as opposed to packages files.
The above will move my config approach from reusing users per differing host to reusing modules which is better practice and better organize my packages on enabling making readability very nice. This does result in more code than if I just created a new packages.nix file for each new user which I could create on demand but this feels better. Also, I am interested in how this turns out.
Generally each workstation device will have 95 to 99% the same config but I want to handle that small percent nicely and copy nicely readable custom module enable code as opposed to packages files.