Skip to content

Conversation

@vic
Copy link
Contributor

@vic vic commented Mar 6, 2025

This also serves as CI test for checking that blueprint correctly integrates home-manager, nixos and nix-darwin configurations.

A new feature is also tested: on host nested home-configurations you can now access hostConfig which provides a way to enable things on home-managed environment based on the host system-wide config.

@vic vic marked this pull request as draft March 6, 2025 22:56
@vic
Copy link
Contributor Author

vic commented Mar 6, 2025

Dunno if this is also related to #77. Using modules to share common settings between different hosts and homes seems natural to me, that's what I'm doing in my systems flake.

@vic vic force-pushed the home-manager-host-config branch from 4c26196 to 2cc9114 Compare March 6, 2025 23:06
@vic
Copy link
Contributor Author

vic commented Mar 6, 2025

Hello, @zimbatm

I was expecting CI to check the nix-darwin configuration defined on this template.

However, checking the output, it seems only the nixos one is being actually checked, even when the flake checks seems to include darwin-configurations.

Screenshot From 2025-03-06 17-19-02

Since the goal of this PR is to exercise more of blueprint's features via CI, I'm wondering if darwin checks are being run on github actions. Am I missing something from the output?

UPDATE: I know what's happening now, sorry. I used x86_64-darwin (same as my old macbook) however CI is running macos-latest which I guess is aarch64-darwin.

@vic vic force-pushed the home-manager-host-config branch from 2cc9114 to 46b84e4 Compare March 7, 2025 00:09
This also serves as CI test for checking that a blueprint correctly
integrates home-manager, nixos and nix-darwin configurations.

A new feature is also tested: on host nested home-configurations you can
now access hostConfig which provides a way to enable things on
home-managed environment based on the host system-wide config.
@vic vic force-pushed the home-manager-host-config branch from 46b84e4 to dca2cd0 Compare March 7, 2025 00:20
@vic vic marked this pull request as ready for review March 7, 2025 00:25
@zimbatm zimbatm merged commit f6a798f into numtide:main Mar 7, 2025
18 checks passed
@zimbatm
Copy link
Member

zimbatm commented Mar 7, 2025

thanks!

@JumpIn-Git
Copy link

JumpIn-Git commented Mar 7, 2025

is the hostConfig specialArg needed, isnt there osConfig for home-manager?

@zimbatm
Copy link
Member

zimbatm commented Mar 7, 2025

Good point, let's remove that

@JumpIn-Git
Copy link

JumpIn-Git commented Mar 7, 2025

the problem is that if you switch to the the hosts user via standalone, osConfig wont exist which will break the home config

edit: dont think this matters

@vic
Copy link
Contributor Author

vic commented Mar 7, 2025

is the hostConfig specialArg needed, isnt there osConfig for home-manager?

Will send another PR to remove hostConfig. Thanks for pointing out to the existing osConfig param from home-manager.

vic added a commit to vic/blueprint that referenced this pull request Mar 7, 2025
`hostConfig` was introduced in numtide#85, however as pointed out by
@JumpIn-Git, home-manager already provides the same functionality via
the `osConfig` module argument.

This PR removes `hostConfig`.

Also added a bit of documentation about the sharing-modules example.
zimbatm pushed a commit that referenced this pull request Mar 7, 2025
`hostConfig` was introduced in #85, however as pointed out by
@JumpIn-Git, home-manager already provides the same functionality via
the `osConfig` module argument.

This PR removes `hostConfig`.

Also added a bit of documentation about the sharing-modules example.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants