standalone home-manager

[HeitorAugustoLN]

@vic do you think this flake should support standalone home-manager configurations? I don't use it myself, but probably there are people out there that use it

[vic]

Yes! definitely, having standalone home-manager is in scope.

I'd also like to support for other configuration classes, like systemManager, and use their system-manager.lib.makeSystemConfig.

if you want to add standalone-hm, feel free to submit a PR, just make sure we have a flake check for it (on the default template, configured in _example).

[vic]

It would be useful if we somehow agree first on the definition syntax, it is currently den.<system>.<hostname>.users.<user>, but what do you propose for standalone users ?

The standalone homeConfigurations.${user.name} should just include self.modules.${user.class}.${user.aspect}.

[vic]

We could have den.hm.<user>, since that is a homeManager specific feature, something like:

den.<system>.homeManager.vic = { aspect = "vic-standalone"; } # see userType in types.nix 

[HeitorAugustoLN]

I was thinking of doing something like den.{hosts,homes}.<system>.<hostname/username> (homes could be just home maybe)

[vic]

cool, I like it, lets go with den.homes.<system>.<user>, and den.hosts.<system>.<host>.users.<user>.

# standalone homes.
den.homes.x86_64-linux.vic = {} # default class is `homeManager` but can be set explicitly.

the standalone hm integration must filter just those users whose class="homeManager" and then create flake.homeConfigurations for them.