diff --git a/index.html b/index.html
index 82d915c1..dacc9913 100644
--- a/index.html
+++ b/index.html
@@ -94,7 +94,8 @@ configured via the home-manager.users.<name>.nixpkgs
instead use the global
pkgs
that is configured via the system level
nixpkgs
options, set
home-manager.useGlobalPkgs = true;
This saves an extra Nixpkgs evaluation, adds consistency, and removes
the dependency on NIX_PATH
, which is otherwise used for importing
-Nixpkgs.
Once installed you can see Chapter 2, Using Home Manager for a more detailed +Nixpkgs.
Home Manager will pass osConfig
as a module argument to any modules
+you create. This contains the system’s NixOS configuration.
{ lib, pkgs, osConfig, ... }:
Once installed you can see Chapter 2, Using Home Manager for a more detailed description of Home Manager and how to use it.
Home Manager provides a module that allows you to prepare user
environments directly from the nix-darwin configuration
file, which often is more convenient than using the home-manager
@@ -127,7 +128,8 @@ configured via the home-manager.users.<name>.nixpkgs
instead use the global
pkgs
that is configured via the system level
nixpkgs
options, set
home-manager.useGlobalPkgs = true;
This saves an extra Nixpkgs evaluation, adds consistency, and removes
the dependency on NIX_PATH
, which is otherwise used for importing
-Nixpkgs.
Once installed you can see Chapter 2, Using Home Manager for a more detailed +Nixpkgs.
Home Manager will pass osConfig
as a module argument to any modules
+you create. This contains the system’s nix-darwin configuration.
{ lib, pkgs, osConfig, ... }:
Once installed you can see Chapter 2, Using Home Manager for a more detailed description of Home Manager and how to use it.
Your use of Home Manager is centered around the configuration file,
which is typically found at ~/.config/home-manager/home.nix
in the standard installation
or ~/.config/home-manager/flake.nix
in a Nix flake based installation.
The default configuration used to be placed in ~/.config/nixpkgs
¸