I did a quick hack on a branch of mine a bit back: master...tgunnoe:nixos-flake:extraModules
The use case is adding colmena along with flake-parts, but extraModules in particular is needed: zhaofengli/colmena#60

Or maybe this needs to be addressed upstream.

Currently this usses myself as a global and only user.

Can machine setips also take a user name (possibly optional) my user name differs on different machines.

In some ways this is the generalisation of issue #19 for none homeManager configs.

I think this means mkLinuxSystem and mkMacosSystem have an optional parameter user that sets myself.

It should look at inputs and filter out those default inputs that do not exist.

cf. #37

https://nix.dev/tutorials/integration-testing-using-virtual-machines

We want to test that running nix run .#activate (on ./examples/*) will do what it is supposed to do.

Similar to https://github.com/srid/haskell-flake/tree/master/example

Should be able to nix flake init it.

We want to support x86_64-darwin as well

Just have nix run .#activate -- --home do this, rather than having a 2nd flake app.

I've just started using this module based on the template with no changes other than my username and hostname.

Whenever I use nix run .#update I get the following warning:

warning: the flag '--update-input nix-darwin' does not match any input

Is there any configuration that needs to be set to avoid this?

Thanks

Presently, when using mkLinuxSystem, the system parameter is look like hardcoded to x86_64-linux.

What should I do if I desire to create host configurations for other architectures like aarch64-linux?

I am try to use nixpkgs.lib.makeOverridable and then update system attribute, but I don't know if that's right because I am Nix noob.

I have noticed that the darwin generator has a system parameter, and I think it might be possible to add a similar parameter to mkLinuxSystem and set a default value to x86_64-linux to keep compatibility with existed configurations.

From https://app.element.io/#/room/#zero-to-flakes:matrix.org

Once NixOS/nixpkgs#251369 is merged

Thanks for this amazing project. I think it's exactly what I've been looking for 💪🏻

I was wondering if some documentation could be added explaining how to use it.
Similar to this explanation: https://github.com/srid/nixos-config#setup

And also an explanation of what would happen next, does a user have to run nix run every time?
How to remove afterwards?

Thanks!

Thank you for these useful templates!

I'd like to use a nixpkgs overlay with this (use a different version of nix). Do you have an example how to use overlays with these templates? In my case I use mkARMMacosSystem.

I'd like to apply the following overlay to nixpkgs:

final: prev: {
  nix = final.nixVersions.nix_2_16;
}

When I created a flake for mac and linux
nix flake check gives me

trace: warning: system.stateVersion is not set, defaulting to 23.05. Read why this matters on https://nixos.org/manual/nixos/stable/options.html#opt-system.stateVersion.

I note that in https://github.com/srid/nixos-config you do set it insystems/darwin.nix and systems/hetzner/ax101.nix - although first is to 4 and other is to a release number.

https://github.com/srid/nixci

cf. https://github.com/juspay/nix-dev-home/blob/b772f2e3408fd3244b1155d41dd86f19dbd61876/home.nix#L25-L28

cf.

❯ > nix store diff-closures /nix/var/nix/profiles/system-151-link /nix/var/nix/profiles/system-152-link
Agda: -1755.7 KiB
ChasingBottoms: -20.8 KiB
JuicyPixels: -97.2 KiB
aeson: +84.2 KiB
aeson-pretty: -8.6 KiB
attoparsec: +18.9 KiB
bifunctors: +33.1 KiB
blaze-html: +8.1 KiB
boring: ∅ → 0.2.1
cmdargs: ∅ → 0.10.22
darwin-system: 23.05.20230406.0e19daa+darwin4.87b9d09 → 23.05.20230411.3fb8eed+darwin4.87b9d09
digest: 0.0.1.6 → 0.0.1.7
doclayout: 0.4 → 0.4.0.1, +50.5 KiB
...

• ublue-os/fleek#156 (comment)
• bketelsen@35f0e1c

cc @bketelsen

Basically add hostname, along with username, to the legacyPackages.homeConfigurations keys.

{
  legacyPackages.homeConfigurations = rec {
    default = ...;
    "srid@macbook1" = default;
    "srid@linux-desktop1" = default;
  };
}

Then nix run .#activate -- --home (see #18) knows which configuration to activate.

Currently, I am trying to track nixpkgs versions separately for different hosts. My old flake.nix had the following:

{
  inputs = {
    # To update nixpkgs (and thus NixOS), pick the nixos-20.09 rev from
    # https://status.nixos.org/
    # (Or, alternatively, nixos-unstable rev.)
    # 
    # 22.05 @21.11.2022
    nixpkgs.url = "github:nixos/nixpkgs/cf63ade6f74bbc9d2a017290f1b2e33e8fbfa70a";
    # 23.11 @07.05.2024
    nixpkgs2.url = "github:nixos/nixpkgs/27c13997bf450a01219899f5a83bd6ffbfc70d3c";
    nixos-wsl.url = "github:nix-community/NixOS-WSL/main";
  };

  outputs = { self, nixpkgs, nixpkgs2, nixos-wsl }: {
    # choice will be done "automatically" based on hostname
    nixosConfigurations.myhost1 = nixpkgs.lib.nixosSystem {
      system = "x86_64-linux";
      modules = [ ./myhost1.nix ];
    };
    nixosConfigurations.myhost2 = nixpkgs2.lib.nixosSystem {
      system = "x86_64-linux";
      modules = [
        nixos-wsl.nixosModules.default
        ./myhost2.nix
      ];
    };
  };
}

I'm trying to port this config to nixos-flake, to let me unify it with my home-manager configs. However, I noticed that nixos-flake seems to be hardcoded to use inputs.nixpkgs, and inputs are passed via flake-parts.lib.mkFlake { inherit inputs; }, so I don't see a clear way to use different nixpkgs between different nixosConfigurations inside nixos-flake. Do you have any suggestions how I could try doing this? I am ok to try modifying nixos-flake code, but I'd be grateful for suggestions how to try approaching that in such case; currently flake-parts is still quite confusing to me; and also you know nixos-flake better, so may have better ideas what approach could be better suited to it.

Might need https://github.com/srid/nixos-config/blob/01d8655b0b2b0f47c2232bb4129789a60d2c82d1/nixos/default.nix#L3-L11 and such things to be upstreamed ....

+ nix run '.#homeConfigurations."john".activationPackage'
warning: creating lock file '/Users/srid/code/nixos-flake/examples/home/flake.lock'
warning: Git tree '/Users/srid/code/nixos-flake' is dirty
Starting Home Manager activation
Error: HOME is set to "/Users/srid/code/nixos-flake/examples/home/tmp/home" but we expect "/Users/john"

cf. nix-community/home-manager#4022

https://nix-community.github.io/home-manager/index.html#sec-install-standalone

How do we modify the .#activate script to account for this case, though?