2023-06-13 23:00:56 +02:00
|
|
|
# copied straight from https://github.com/hercules-ci/flake-parts/blob/main/modules/nixosConfigurations.nix
|
2024-03-02 22:05:30 +01:00
|
|
|
{
|
|
|
|
lib,
|
|
|
|
flake-parts-lib,
|
|
|
|
...
|
|
|
|
}: let
|
|
|
|
inherit
|
|
|
|
(lib)
|
2023-06-13 23:00:56 +02:00
|
|
|
mkOption
|
|
|
|
types
|
|
|
|
literalExpression
|
|
|
|
;
|
2024-03-02 22:05:30 +01:00
|
|
|
inherit
|
|
|
|
(flake-parts-lib)
|
2023-06-13 23:00:56 +02:00
|
|
|
mkSubmoduleOptions
|
|
|
|
;
|
2024-03-02 22:05:30 +01:00
|
|
|
in {
|
2023-06-13 23:00:56 +02:00
|
|
|
options = {
|
|
|
|
flake = mkSubmoduleOptions {
|
|
|
|
nixngConfigurations = mkOption {
|
|
|
|
type = types.lazyAttrsOf types.raw;
|
2024-03-02 22:05:30 +01:00
|
|
|
default = {};
|
2023-06-13 23:00:56 +02:00
|
|
|
description = ''
|
|
|
|
Instantiated NixNG configurations.
|
|
|
|
`nixngConfigurations` is for specific machines. If you want to expose
|
|
|
|
reusable configurations, add them to [`nixosModules`](#opt-flake.nixosModules)
|
|
|
|
in the form of modules (no `lib.nixosSystem`), so that you can reference
|
|
|
|
them in this or another flake's `nixngConfigurations`.
|
|
|
|
'';
|
|
|
|
};
|
|
|
|
};
|
|
|
|
};
|
|
|
|
}
|