Skip to content
This repository has been archived by the owner on Aug 5, 2024. It is now read-only.

Un-abstract the configuration #20

Closed
NotAShelf opened this issue Aug 13, 2023 · 1 comment
Closed

Un-abstract the configuration #20

NotAShelf opened this issue Aug 13, 2023 · 1 comment

Comments

@NotAShelf
Copy link
Owner

As pointed countless time before, my configuration is overly abstracted in favor of it making sense to me. Might consider compromising on it making sense and follow certain nix principles.

Patterns I will not follow:

1. abusing lib.nixosSystem

hostName = nixpkgs.lib.nixosSystem {
    modules = [
    	../modules/desktop/foo.nix
		../modules/desktop/bar.nix
		../modules/hardware/baz.nix
		../home/notashelf		
    ];
};

Simply a very ugly way of structuring my hosts, which I have many of. At this point, abstractions start seeming nice.

2. whatever this is

# configuration.nix
imports = [
	../modules/desktop/foo.nix
	../modules/desktop/bar.nix
	../modules/hardware/baz.nix
	../home/notashelf
];

Declaring modules and importing them at host level (as in each hosts's own configuration.nix) forces me to play mental gymnastics with capabilities of each host.

image

In short, nuh uh.

@NotAShelf
Copy link
Owner Author

Fuck it, I'll abstract it even more than before.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant