Home Manager - Revision history

Дима: Fix probable typo

2026-05-12T19:11:02Z

Fix probable typo

← Older revision		Revision as of 19:11, 12 May 2026
Line 2:		Line 2:
	* install software declaratively in your user profile, rather than using nix-env		* install software declaratively in your user profile, rather than using nix-env
	* manage dotfiles in the home directory of your user.		* manage dotfiles in the home directory of your user.
	Home Manager has many [https://nix-community.github.io/home-manager/options.xhtml options], which can look daunting at first, but most of those options only boil down to creating some dotfiles and installing some software in a ~~way~~ similar way to nix-env.		Home Manager has many [https://nix-community.github.io/home-manager/options.xhtml options], which can look daunting at first, but most of those options only boil down to creating some dotfiles and installing some software in a similar way to nix-env.

	{{Note\|Before attempting to use Home Manager [https://github.com/rycee/home-manager#words-of-warning please read the warning].}}		{{Note\|Before attempting to use Home Manager [https://github.com/rycee/home-manager#words-of-warning please read the warning].}}

Malix: fix: name standardization

2025-11-07T22:11:54Z

fix: name standardization

← Older revision		Revision as of 22:11, 7 November 2025
Line 16:		Line 16:
	Your configuration is stored in <code>~/.config/home-manager/home.nix</code>. Each time you modify it, rerun <code>home-manager switch</code> for changes to have effect.		Your configuration is stored in <code>~/.config/home-manager/home.nix</code>. Each time you modify it, rerun <code>home-manager switch</code> for changes to have effect.

	To work correctly, ~~home-manager~~ needs your shell to source <code>~/.nix-profile/etc/profile.d/hm-session-vars.sh</code>. The most convenient way to do so is to have ~~home-manager~~ manage your whole shell configuration, eg <code>programs.bash.enable = true;</code> or <code>programs.zsh.enable = true;</code>. But in this case your whole bashrc is managed with Home Manager: the years of customization you accumulated in your former .bashrc must be migrated to Home Manager options, which may take some time. The quick and dirty way to do the migration is to move your bashrc to some other location and source it from Home Manager:		To work correctly, Home Manager needs your shell to source <code>~/.nix-profile/etc/profile.d/hm-session-vars.sh</code>. The most convenient way to do so is to have Home Manager manage your whole shell configuration, eg <code>programs.bash.enable = true;</code> or <code>programs.zsh.enable = true;</code>. But in this case your whole bashrc is managed with Home Manager: the years of customization you accumulated in your former .bashrc must be migrated to Home Manager options, which may take some time. The quick and dirty way to do the migration is to move your bashrc to some other location and source it from Home Manager:
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	{ pkgs, ...}: {		{ pkgs, ...}: {
Line 50:		Line 50:
	It can either be incorporated in <code>/etc/nixos/configuration.nix</code> or be placed in a standalone file and imported in configuration.nix: <code>imports = [ ./thefile.nix ]</code>.		It can either be incorporated in <code>/etc/nixos/configuration.nix</code> or be placed in a standalone file and imported in configuration.nix: <code>imports = [ ./thefile.nix ]</code>.

	Whenever you change you ~~home-manager~~ configuration, you must rerun <code>nixos-rebuild switch</code>. With this method, changing the configuration of an unprivileged user requires to run a command as root.		Whenever you change you Home Manager configuration, you must rerun <code>nixos-rebuild switch</code>. With this method, changing the configuration of an unprivileged user requires to run a command as root.

	=== Usage as a NixOS module in a Flake ===		=== Usage as a NixOS module in a Flake ===
Line 89:		Line 89:
	</syntaxhighlight>		</syntaxhighlight>

	Here's an example of ~~home manager~~ configuration in ./home.nix		Here's an example of Home Manager configuration in ./home.nix
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	{ config, pkgs, ... }:		{ config, pkgs, ... }:
Line 108:		Line 108:
	Of course you'll probably want to keep more stuff in there than just a state version, but the state version is required.		Of course you'll probably want to keep more stuff in there than just a state version, but the state version is required.

	The downside to doing it this way over the User config is that you have to do a full system rebuild; the ~~home manager~~ config is part of the full system, and so must be built as root or at least a trusted user.		The downside to doing it this way over the User config is that you have to do a full system rebuild; the Home Manager config is part of the full system, and so must be built as root or at least a trusted user.

	== Usage ==		== Usage ==
Line 117:		Line 117:
	<code>nix-env -i jdk8</code>, running <code>nix-env --upgrade</code> upgrades java to 10 despite the fact that we initially explicitly requested java 8.		<code>nix-env -i jdk8</code>, running <code>nix-env --upgrade</code> upgrades java to 10 despite the fact that we initially explicitly requested java 8.

	Installing software with Home~~-manager~~ avoids this problem:		Installing software with Home Manager avoids this problem:
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	{ pkgs, ...}: {		{ pkgs, ...}: {
Line 124:		Line 124:
	</syntaxhighlight>		</syntaxhighlight>

	It is a perfectly valid use case for ~~home-manager~~ to only install software with <code>home.packages</code> without managing dotfiles at all.		It is a perfectly valid use case for Home Manager to only install software with <code>home.packages</code> without managing dotfiles at all.

	=== Usage on non-NixOS Linux ===		=== Usage on non-NixOS Linux ===
Line 163:		Line 163:
	{{Note\|In both ways ("source" and "text"), the symlink points to a target in /nix/store. The difference is that, "source" would overwrite the content of the dot file, while "text" would add the text to the dot file that may also be affected in other places.}}		{{Note\|In both ways ("source" and "text"), the symlink points to a target in /nix/store. The difference is that, "source" would overwrite the content of the dot file, while "text" would add the text to the dot file that may also be affected in other places.}}

	You have the whole list of the options available in ~~home-manager~~ [https://nix-community.github.io/home-manager/options.xhtml here]		You have the whole list of the options available in Home Manager [https://nix-community.github.io/home-manager/options.xhtml here]

	=== Examples ===		=== Examples ===
Line 173:		Line 173:
	== FAQ ==		== FAQ ==

	=== I cannot set GNOME or Gtk themes via ~~home-manager~~ ===		=== I cannot set GNOME or Gtk themes via Home Manager ===

	If you get [https://nix-community.github.io/home-manager/index.xhtml#_why_do_i_get_an_error_message_about_literal_ca_desrt_dconf_literal_or_literal_dconf_service_literal an error about {{ic\|ca.desrt.conf}} or {{ic\|dconf.service}}] on NixOS, add		If you get [https://nix-community.github.io/home-manager/index.xhtml#_why_do_i_get_an_error_message_about_literal_ca_desrt_dconf_literal_or_literal_dconf_service_literal an error about {{ic\|ca.desrt.conf}} or {{ic\|dconf.service}}] on NixOS, add
Line 187:		Line 187:
	=== Workaround with <code>home on tmpfs</code> and standalone installation ===		=== Workaround with <code>home on tmpfs</code> and standalone installation ===

	home-on-tmpfs users who installed ~~home-manager~~ standalone may meet problems that cannot load configs after reboot, caused by auto cleaning symlink under the toplevel of the home directory. You need to ensure <code>/home/<user>/.nix-profile</code> exists since the standalone install will not act symlink while the system boots.		home-on-tmpfs users who installed Home Manager standalone may meet problems that cannot load configs after reboot, caused by auto cleaning symlink under the toplevel of the home directory. You need to ensure <code>/home/<user>/.nix-profile</code> exists since the standalone install will not act symlink while the system boots.

	If your toplevel of home is on tmpfs, one possible workaround is manually write <code>activationScripts</code> to link the directory:		If your toplevel of home is on tmpfs, one possible workaround is manually write <code>activationScripts</code> to link the directory:
Line 206:		Line 206:
	== Templates ==		== Templates ==

	* https://github.com/juspay/nix-dev-home A ~~home-manager~~ template providing useful tools & settings for Nix-based development.		* https://github.com/juspay/nix-dev-home A Home Manager template providing useful tools & settings for Nix-based development.

	== Alternatives ==		== Alternatives ==

Malix: general flake enhancements

2025-11-03T23:47:32Z

general flake enhancements

← Older revision		Revision as of 23:47, 3 November 2025
Line 75:		Line 75:
	modules = [		modules = [
	./configuration.nix		./configuration.nix
	home-manager.nixosModules.~~home-manager~~		home-manager.nixosModules.default
	{		{
	home-manager.useGlobalPkgs = true;		home-manager = {
	~~home-manager.~~useUserPackages = true;		useGlobalPkgs = true;
	~~home-manager.~~users.<USERNAME> = ./home.nix; # replace <USERNAME> with your actual username		useUserPackages = true;
			users.<USERNAME> = ./home.nix; # replace <USERNAME> with your actual username
			};
	}		}
	];		];
Line 140:		Line 142:
	enable = true;		enable = true;
	settings = {		settings = {
	user.name = "my_git_username";		user = {
	~~user.~~email = "my_git_username@gmail.com";		name = "my_git_username";
			email = "my_git_username@gmail.com";
			};
	};		};
	};		};

Woile: git userEmail and userName has been deprecated in favor of settings.user.name and settings.user.email. See https://github.com/nix-community/home-manager/pull/8006/files#diff-9fbbe27a20e0a8631ca585407d756283d49e294a6d856e820626a886a6853248

2025-10-29T10:50:38Z

git userEmail and userName has been deprecated in favor of settings.user.name and settings.user.email. See https://github.com/nix-community/home-manager/pull/8006/files#diff-9fbbe27a20e0a8631ca585407d756283d49e294a6d856e820626a886a6853248

← Older revision		Revision as of 10:50, 29 October 2025
Line 139:		Line 139:
	programs.git = {		programs.git = {
	enable = true;		enable = true;
	~~userName~~ = "my_git_username";		settings = {
	~~userEmail~~ = "my_git_username@gmail.com";		user.name = "my_git_username";
			user.email = "my_git_username@gmail.com";
			};
	};		};
	</syntaxhighlight>		</syntaxhighlight>

Malix: /* Using Home Manager as a declarative version of nix-env */ enhance title

2025-10-24T23:04:35Z

Using Home Manager as a declarative version of nix-env: enhance title

← Older revision		Revision as of 23:04, 24 October 2025
Line 110:		Line 110:
	== Usage ==		== Usage ==

	=== Using Home Manager ~~as a declarative version of nix-env~~ ===		=== Using Home Manager to install package declaratively ===

	Nix-env has problematic behavior due to its imperative nature. For example, after installing java 8 with		Nix-env has problematic behavior due to its imperative nature. For example, after installing java 8 with

Malix: /* Usage as a NixOS module in a Flake */ fix

2025-10-24T19:56:25Z

Usage as a NixOS module in a Flake: fix

← Older revision		Revision as of 19:56, 24 October 2025
Line 57:		Line 57:
	{		{
	inputs = {		inputs = {
	nixpkgs.url = "github:NixOS/nixpkgs/nixos-24.11";		nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.05";
	home-manager = {		home-manager = {
	url = "github:nix-community/home-manager/release-24.11";		url = "github:nix-community/home-manager/release-25.05";
	inputs.nixpkgs.follows = "nixpkgs";		inputs.nixpkgs.follows = "nixpkgs";
	};		};
	};		};
	outputs = { self, nixpkgs, home-manager, ... }@inputs:		outputs =
	nixosConfigurations.~~exampleMachine~~ = ~~nixosConfiguration "exampleMachine"~~		{
	system = "x86_64-linux";		self,
	modules = [		nixpkgs,
	./configuration.nix		home-manager,
	home-manager.nixosModules.home-manager		...
	{		}@inputs:
	home-manager.useGlobalPkgs = true;		{
	home-manager.useUserPackages = true;		nixosConfigurations.<HOSTNAME> = nixpkgs.lib.nixosSystem { # replace <HOSTNAME> with your actual hostname
	home-manager.users.~~your-username~~ = ~~import~~ ./home.nix;		system = "x86_64-linux";
	}		modules = [
	];		./configuration.nix
			home-manager.nixosModules.home-manager
			{
			home-manager.useGlobalPkgs = true;
			home-manager.useUserPackages = true;
			home-manager.users.<USERNAME> = ./home.nix; # replace <USERNAME> with your actual username
			}
			];
			};
	};		};
	};
	}		}
	</syntaxhighlight>		</syntaxhighlight>

Aaronchall: remove "note that" - this wiki is all notes and it is redundant

2025-09-11T03:34:54Z

remove "note that" - this wiki is all notes and it is redundant

← Older revision		Revision as of 03:34, 11 September 2025
Line 16:		Line 16:
	Your configuration is stored in <code>~/.config/home-manager/home.nix</code>. Each time you modify it, rerun <code>home-manager switch</code> for changes to have effect.		Your configuration is stored in <code>~/.config/home-manager/home.nix</code>. Each time you modify it, rerun <code>home-manager switch</code> for changes to have effect.

	~~Note that to~~ work correctly, home-manager needs your shell to source <code>~/.nix-profile/etc/profile.d/hm-session-vars.sh</code>. The most convenient way to do so is to have home-manager manage your whole shell configuration, eg <code>programs.bash.enable = true;</code> or <code>programs.zsh.enable = true;</code>. But in this case your whole bashrc is managed with Home Manager: the years of customization you accumulated in your former .bashrc must be migrated to Home Manager options, which may take some time. The quick and dirty way to do the migration is to move your bashrc to some other location and source it from Home Manager:		To work correctly, home-manager needs your shell to source <code>~/.nix-profile/etc/profile.d/hm-session-vars.sh</code>. The most convenient way to do so is to have home-manager manage your whole shell configuration, eg <code>programs.bash.enable = true;</code> or <code>programs.zsh.enable = true;</code>. But in this case your whole bashrc is managed with Home Manager: the years of customization you accumulated in your former .bashrc must be migrated to Home Manager options, which may take some time. The quick and dirty way to do the migration is to move your bashrc to some other location and source it from Home Manager:
	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">
	{ pkgs, ...}: {		{ pkgs, ...}: {

NobbZ: Removed options that are not only not needed for HM as system module, but might be harmful when used (wrong)

2025-07-16T12:54:19Z

Removed options that are not only not needed for HM as system module, but might be harmful when used (wrong)

← Older revision		Revision as of 12:54, 16 July 2025
Line 85:		Line 85:

	{		{
	~~# Home Manager needs a bit of information about you and the~~
	~~# paths it should manage.~~
	~~home.username = "your-username";~~
	~~home.homeDirectory = "/home/your-username";~~

	# This value determines the Home Manager release that your		# This value determines the Home Manager release that your
	# configuration is compatible with. This helps avoid breakage		# configuration is compatible with. This helps avoid breakage
Line 99:		Line 94:
	# changes in each release.		# changes in each release.
	home.stateVersion = "24.11";		home.stateVersion = "24.11";

	~~# Let Home Manager install and manage itself.~~
	~~programs.home-manager.enable = true;~~
	}		}
	</syntaxhighlight>		</syntaxhighlight>

Ingenarel: (fix): syntax error

2025-04-08T23:47:44Z

(fix): syntax error

← Older revision		Revision as of 23:47, 8 April 2025
Line 67:		Line 67:
	system = "x86_64-linux";		system = "x86_64-linux";
	modules = [		modules = [
	./configuration.nix		./configuration.nix
	home-manager.nixosModules.home-manager		home-manager.nixosModules.home-manager
	{		{
	home-manager.useGlobalPkgs = true;		home-manager.useGlobalPkgs = true;
	home-manager.useUserPackages = true;		home-manager.useUserPackages = true;
	home-manager.users.your-username = import ./home.nix;		home-manager.users.your-username = import ./home.nix;
	};		}
	];		];
	};		};

Rrdpad: fix: added semicolon

2024-12-14T10:42:58Z

fix: added semicolon

← Older revision		Revision as of 10:42, 14 December 2024
Line 60:		Line 60:
	home-manager = {		home-manager = {
	url = "github:nix-community/home-manager/release-24.11";		url = "github:nix-community/home-manager/release-24.11";
	inputs.nixpkgs.follows = "nixpkgs"		inputs.nixpkgs.follows = "nixpkgs";
	};		};
	};		};