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

Un-abstract the configuration #20

Closed
@NotAShelf

Description

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.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions