Appendix B. NixOS Configuration Options

Whether to enable legacy profile management during activation. When enabled, the Home Manager activation will produce a per-user home-manager Nix profile, just like in the standalone installation of Home Manager. Typically, this is not desired when Home Manager is embedded in the system configuration.

Type: boolean

Default: false

Declared by:

On activation run this command on each existing file rather than exiting with an error.

Type: null or string or absolute path

Default: null

Example: ''${pkgs.trash-cli}/bin/trash

Declared by:

On activation move existing files by appending the given file extension rather than exiting with an error.

Type: null or string

Default: null

Example: "backup"

Declared by:

Extra specialArgs passed to Home Manager. This option can be used to pass additional arguments to all modules.

Type: attribute set

Default: { }

Example: { inherit emacs-overlay; }

Declared by:

Whether to enable forced overwriting of existing backup files when using backupFileExtension .

Type: boolean

Default: false

Example: true

Declared by:

Extra modules added to all users.

Type: list of raw value

Default: [ ]

Example: [ { home.packages = [ nixpkgs-fmt ]; } ]

Declared by:

Whether to enable using the system configuration’s pkgs argument in Home Manager. This disables the Home Manager options nixpkgs.*.

Type: boolean

Default: false

Example: true

Declared by:

Whether to enable installation of user packages through the users.users.<name>.packages option.

Type: boolean

Default: false

Example: true

Declared by:

Per-user Home Manager configuration.

Type: attribute set of (Home Manager module)

Default: { }

Declared by:

Whether to enable verbose output on activation.

Type: boolean

Default: false

Example: true

Declared by: