I want to nix flake init --template github:mincik/nix-forge and it generates a flake.nix like¹:
{
description = "Your Nix Forge";
inputs.nix-forge.url = "github:mincik/nix-forge";
outputs = {self, ...}@inputs: inputs.nix-forge.load [ ./recipes "${inputs.nix-forge}/apps/nix-forge/" ];
}
or nix flake init --template github:mincik/nix-forge#flake-parts, and it generates a flake.nix like¹:
{
description = "Your Flake Part with Forge";
inputs.flake-parts.url = "github:hercules-ci/flake-parts";
inputs.nixForge.url = "github:mincik/nix-forge";
outputs = {self, ...}@inputs:
inputs.flake-parts.lib.mkFlake { inherit inputs; } {
_module.args.rootPath = ./.;
systems = [ "x86_64-linux" ];
imports = [
${inputs.nix-forge}/modules/
${inputs.nix-forge}/recipes/apps/nix-forge/ # #41
./recipes/
];
};
}
And add ./recipes/default.nix, ./recipes/packages/helloPkg/recipe.nix, ./recipes/apps/helloApp/recipe.nix
¹ this is a feature request, so it don't have to be exactly like this, but please keep it simple as possible, we don't want to scare our users.
Hope this helps people start using the forge as a dependency instead of a clone, making them less afraid and more aware of how it is useful.
see also #41
I want to
nix flake init --template github:mincik/nix-forgeand it generates a flake.nix like¹:or
nix flake init --template github:mincik/nix-forge#flake-parts, and it generates a flake.nix like¹:And add ./recipes/default.nix, ./recipes/packages/helloPkg/recipe.nix, ./recipes/apps/helloApp/recipe.nix
¹ this is a feature request, so it don't have to be exactly like this, but please keep it simple as possible, we don't want to scare our users.
Hope this helps people start using the forge as a dependency instead of a clone, making them less afraid and more aware of how it is useful.
see also #41