Skip to content
/ dendrix Public

Mention flake-file on minimalistic flake.nix section #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vic merged 1 commit into from
Oct 16, 2025
Merged

Mention flake-file on minimalistic flake.nix section #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 9 additions & 7 deletions dev/book/src/Dendritic.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -120,18 +120,20 @@ This means we can have:

### Minimal and focused flake.nix

Instead of having huge `flake.nix` files with lots of nix logic inside the flake itself.
It is now possible move to all nix logic into `./modules`.
Instead of having huge `flake.nix` files with lots of nix logic inside. It is now possible
to move all nix logic into well organized auto-imported flake-parts in `./modules`. This way, `flake.nix` serves more as a manifest of dependencies and flake entrypoint.
Copy link

Copilot AI Oct 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing word 'well-organized' should be hyphenated for proper grammar.

Suggested change
to move all nix logic into well organized auto-imported flake-parts in `./modules`. This way, `flake.nix` serves more as a manifest of dependencies and flake entrypoint.
to move all nix logic into well-organized auto-imported flake-parts in `./modules`. This way, `flake.nix` serves more as a manifest of dependencies and flake entrypoint.

Copilot uses AI. Check for mistakes.
Copy link

Copilot AI Oct 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing article 'a' before 'flake entrypoint'.

Suggested change
to move all nix logic into well organized auto-imported flake-parts in `./modules`. This way, `flake.nix` serves more as a manifest of dependencies and flake entrypoint.
to move all nix logic into well organized auto-imported flake-parts in `./modules`. This way, `flake.nix` serves more as a manifest of dependencies and a flake entrypoint.

Copilot uses AI. Check for mistakes.

Your flake becomes minimal, focused on defining inputs and possibly cache, experimental-features config.
Some people go a step further and use [vic/flake-file](https://github.com/vic/flake-file) to manage their flake.nix automatically, by letting each flake-part module also define the flake inputs needed by each module.

And any file inside modules can contribute to flake outputs (packages/checks/osConfigurations) as needed.
Any flake-parts module can contribute to flake.nix as needed, either inputs/flake-configuration (by using `vic/flake-file`) or outputs (modules/packages/checks/osConfigurations/etc).

```nix
# modules/flake/formatter.nix
# ./modules/home/vim.nix
{ inputs, ... }:
{
perSystem = {pkgs, ...}: {
formatter = pkgs.alejandra;
flake-file.inputs.nixvim.url = "github:nix-community/nixvim";
flake.modules.homeManager.vim = {
# use inputs.nixvim
};
}
```
Expand Down
Loading