NixOS system configuration - Revision history

Pandapip1: Right, that also needs buildPackages

2026-07-22T22:45:42Z

Right, that also needs buildPackages

← Older revision		Revision as of 22:45, 22 July 2026
Line 258:		Line 258:
	narHash = builtins.readFile		narHash = builtins.readFile
	(pkgs.buildPackages.runCommandLocal "get-nixpkgs-hash"		(pkgs.buildPackages.runCommandLocal "get-nixpkgs-hash"
	{ nativeBuildInputs = [ pkgs.nix ]; }		{ nativeBuildInputs = [ pkgs.buildPackages.nix ]; }
	"nix-hash --type sha256 --sri ${pkgs.path} > $out");		"nix-hash --type sha256 --sri ${pkgs.path} > $out");
	};		};

Pandapip1: Correctly use buildPackages to avoid broken cross

2026-07-22T22:44:04Z

Correctly use buildPackages to avoid broken cross

← Older revision		Revision as of 22:44, 22 July 2026
Line 257:		Line 257:
	path = pkgs.path;		path = pkgs.path;
	narHash = builtins.readFile		narHash = builtins.readFile
	(pkgs.runCommandLocal "get-nixpkgs-hash"		(pkgs.buildPackages.runCommandLocal "get-nixpkgs-hash"
	{ nativeBuildInputs = [ pkgs.nix ]; }		{ nativeBuildInputs = [ pkgs.nix ]; }
	"nix-hash --type sha256 --sri ${pkgs.path} > $out");		"nix-hash --type sha256 --sri ${pkgs.path} > $out");
Line 263:		Line 263:
	};		};
	</nowiki>		</nowiki>
	}}		\|name=\|lang=}}

	This has the unfortunate side-effect of requiring import-from-derivation and slowing down build times, however it may greatly speed up almost every eval. Full-time flakes users may be able to just use <code>narHash = pkgs.narHash</code>.		This has the unfortunate side-effect of requiring import-from-derivation and slowing down build times, however it may greatly speed up almost every eval. Full-time flakes users may be able to just use <code>narHash = pkgs.narHash</code>.

Stinker-Heavy: removed the carets in nixosConifgurations."hostname" because they were breaking and showing nonsense characters.

2026-06-17T03:36:12Z

removed the carets in nixosConifgurations."hostname" because they were breaking and showing nonsense characters.

← Older revision		Revision as of 03:36, 17 June 2026
Line 180:		Line 180:
	==== Importing packages from multiple nixpkgs branches ====		==== Importing packages from multiple nixpkgs branches ====

	A NixOS config flake could be as follows (replace <hostname> with your hostname):		A NixOS config flake could be as follows (replace hostname with your hostname):

	{{file\|3=<nowiki>		{{file\|3=<nowiki>
Line 194:		Line 194:
	{ nixpkgs, nixpkgs-unstable, ... }:		{ nixpkgs, nixpkgs-unstable, ... }:
	{		{
	nixosConfigurations."<hostname>" = nixpkgs.lib.nixosSystem {		nixosConfigurations."hostname" = nixpkgs.lib.nixosSystem {
	modules = [		modules = [
	{		{

Toastal: Remove the word “modern” for an experimental API as it suggests stable code is not modern

2026-05-22T16:27:11Z

Remove the word “modern” for an experimental API as it suggests stable code is not modern

← Older revision		Revision as of 16:27, 22 May 2026
Line 59:		Line 59:
	== Defining NixOS as a flake ==		== Defining NixOS as a flake ==

	[[Flakes]] offer an alternative~~, modern~~ way to configure NixOS systems using a standardized and reproducible structure. With flakes, the system configuration — along with any additional inputs such as Nixpkgs or external modules — is managed declaratively within a <code>flake.nix</code> file.		[[Flakes]] offer an alternative way to configure NixOS systems using a standardized and reproducible structure. With flakes, the system configuration — along with any additional inputs such as Nixpkgs or external modules — is managed declaratively within a <code>flake.nix</code> file.

	Unlike the traditional configuration model, which relies on <code>/etc/nixos/configuration.nix</code> and channels, flakes explicitly define their dependencies and configurations, making it easier to share, version, and reproduce complete NixOS system setups.		Unlike the traditional configuration model, which relies on <code>/etc/nixos/configuration.nix</code> and channels, flakes explicitly define their dependencies and configurations, making it easier to share, version, and reproduce complete NixOS system setups.

DHCP: /* Getting Instant System Flakes Repl */ use lang=nix for `nix repl` snippet syntax highlighting. Although a "hack", i find it more readable. If i'm wrong, feel free to revert

2026-05-20T23:11:05Z

Getting Instant System Flakes Repl: use lang=nix for `nix repl` snippet syntax highlighting. Although a "hack", i find it more readable. If i'm wrong, feel free to revert

← Older revision		Revision as of 23:11, 20 May 2026
Line 271:		Line 271:
	How to get a nix repl out of your system flake:		How to get a nix repl out of your system flake:

	<syntaxhighlight lang="~~text~~">		<syntaxhighlight lang="nix">
	$ nix repl		$ nix repl

Rpqt: Add quotes to URL literals

2026-01-26T12:30:47Z

Add quotes to URL literals

← Older revision		Revision as of 12:30, 26 January 2026
Line 70:		Line 70:
	<nowiki>		<nowiki>
	{		{
	inputs.nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;		inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
	outputs = { self, nixpkgs }: {		outputs = { self, nixpkgs }: {
	# replace 'joes-desktop' with your hostname here.		# replace 'joes-desktop' with your hostname here.
Line 87:		Line 87:
	{{file\|flake.nix\|nix\|<nowiki>		{{file\|flake.nix\|nix\|<nowiki>
	{		{
	inputs.nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;		inputs.nixpkgs.url = "github:NixOS/nixpkgs/nixos-unstable";
	inputs.home-manager.url = github:nix-community/home-manager;		inputs.home-manager.url = "github:nix-community/home-manager";

	outputs = { self, nixpkgs, ... }@inputs: {		outputs = { self, nixpkgs, ... }@inputs: {

Asdfer: edit "more through" -> more thorough

2026-01-21T07:28:55Z

edit "more through" -> more thorough

← Older revision		Revision as of 07:28, 21 January 2026
Line 1:		Line 1:
	[[NixOS]] uses a declarative configuration system that allows users to manage their entire operating system setup including installed packages, system services, user accounts, hardware settings, and more ~~through~~ configuration files. This page serves as an overview of how to work with and manage NixOS system configurations.		[[NixOS]] uses a declarative configuration system that allows users to manage their entire operating system setup including installed packages, system services, user accounts, hardware settings, and more thorough configuration files. This page serves as an overview of how to work with and manage NixOS system configurations.

	For an introduction to declarative configuration, see the [[Overview of the NixOS Linux distribution#Declarative Configuration]] and the {{NixOS Manual\|name=NixOS official manual\|anchor=#ch-configuration}}.		For an introduction to declarative configuration, see the [[Overview of the NixOS Linux distribution#Declarative Configuration]] and the {{NixOS Manual\|name=NixOS official manual\|anchor=#ch-configuration}}.

Starfish2228: /* Importing packages from multiple nixpkgs branches */ fix overlay to respect existing config/system

2026-01-19T17:19:16Z

Importing packages from multiple nixpkgs branches: fix overlay to respect existing config/system

← Older revision		Revision as of 17:19, 19 January 2026
Line 187:		Line 187:

	inputs = {		inputs = {
	nixpkgs.url = "github:NixOS/nixpkgs/nixos-24.11";		nixpkgs.url = "github:NixOS/nixpkgs/nixos-25.11";
	nixpkgs-unstable.url = "github:NixOS/nixpkgs/nixos-unstable";		nixpkgs-unstable.url = "github:NixOS/nixpkgs/nixos-unstable";
	};		};
Line 199:		Line 199:
	nixpkgs.overlays = [		nixpkgs.overlays = [
	(final: prev: {		(final: prev: {
	~~unstable = nixpkgs-unstable.legacyPackages.${prev.system};~~		unstable = import nixpkgs-unstable {
	~~# use this variant if unfree packages are needed:~~		inherit (final) config;
	# unstable = import nixpkgs-unstable {		inherit (final.stdenv.hostPlatform) system;
	# inherit ~~prev~~;		};
	~~# system = prev~~.system;
	~~# config.allowUnfree = true;~~
	# };
	})		})
	];		];

Volse01: minor fix of typo

2025-09-26T17:30:13Z

minor fix of typo

← Older revision		Revision as of 17:30, 26 September 2025
Line 333:		Line 333:
	* [[Updating NixOS]] - Updating the set of [[Nixpkgs]] the system uses		* [[Updating NixOS]] - Updating the set of [[Nixpkgs]] the system uses

	* [[NixOS as a ~~dekstop~~]] - Configuration tips for setting up NixOS as a desktop		* [[NixOS as a desktop]] - Configuration tips for setting up NixOS as a desktop

	* [[Nixos-rebuild]] - Command to apply changes to system configuration		* [[Nixos-rebuild]] - Command to apply changes to system configuration

Malix: /* Flake-specific tips */ update code snippets

2025-09-06T19:40:08Z

Flake-specific tips: update code snippets

← Older revision		Revision as of 19:40, 6 September 2025
Line 182:		Line 182:
	A NixOS config flake could be as follows (replace <hostname> with your hostname):		A NixOS config flake could be as follows (replace <hostname> with your hostname):

	{{file\|~~flake.nix\|nix\|~~<nowiki>		{{file\|3=<nowiki>
	{		{
	description = "NixOS configuration with two or more channels";		description = "NixOS configuration with two or more channels";
Line 214:		Line 214:
	};		};
	}		}
	</nowiki>		</nowiki>\|name=/etc/nixos/flake.nix\|lang=nix}}
	}}

	{{file\|~~flake.nix\|nix\|~~<nowiki>		{{file\|3=<nowiki>
	# can now use "pkgs.package" or "pkgs.unstable.package"		# can now use "pkgs.package" or "pkgs.unstable.package"
	{ pkgs, ... }:		{ pkgs, ... }:
Line 227:		Line 226:
	# ...		# ...
	}		}
	</nowiki>		</nowiki>\|name=/etc/nixos/configuration.nix\|lang=nix}}
	}}

	If the variable <code>nixpkgs</code> points to the flake, you can also define <code>pkgs</code> with overlays with:		If the variable <code>nixpkgs</code> points to the flake, you can also define <code>pkgs</code> with overlays with: