Modular Services - Revision history

Eveeifyeve: fix: references

2026-07-14T01:56:13Z

fix: references

← Older revision		Revision as of 01:56, 14 July 2026
Line 33:		Line 33:


	== ~~References~~ ==		== Resources ==

	~~<references />~~
			{{Cleanup\|reason=More information is needed.}}

			# {{manual\|nixos\|modular-services\|NixOS Modular Services\|subsection=modular-services}}
			# {{issue \| 428084 \| Tracking issue}}

Eveeifyeve: Added some information to wiki

2026-07-14T01:46:20Z

Added some information to wiki

← Older revision	Revision as of 01:46, 14 July 2026
Line 1:	Line 1:
		{{warning \| Work in progress }}

		Modular Services are a new experimental module system support in Nixpkgs, that aims to expand the module systems (Eg. NixOS, home-manager, nix-darwin, etc) ecosystem with modularity and portability. Modular services is designed to integrate/compose with other modules systems such as NixOS.

		== Difference between Traditional Module Systems (such as NixOS) vs Modular Services ==

		Modular services are built for composability, re-usability, are not defined in sets of options, portable.
		Where as traditional modules are the opposite.

		== How to use ==

		* System:

		<syntaxhighlight lang="nix">
		system.services.<name> = {
		# Usage inside of the traditional module system like NixOS...
		imports = [ pkgs.example.services.default ];
		example.allowAll = false;
		};
		</syntaxhighlight>

		* User:

		{{warning \| Not all module systems support this, like for example NixOS.}}

		<syntaxhighlight lang="nix">
		system.user.services.<name> = {
		# Usage inside of the traditional module system like NixOS...
		imports = [ pkgs.example.services.default ];
		example.allowAll = false;
		};
		</syntaxhighlight>


		== References ==

		<references />

Ehmry: not appropriate

2025-09-11T07:42:08Z

not appropriate

← Older revision		Revision as of 07:42, 11 September 2025
Line 1:		Line 1:
	~~Modular services are an experimental feature added to NixOS between the 25.05 and 25.11 releases.~~

	~~For official documentation see the [https://nixos.org/manual/nixos/unstable/#modular-services NixOS Manual].~~

	~~This page exists to used to collect experiences and recommendations for using this feature that would not fit well in the NixOS manual.~~

	~~== Do's ==~~

	~~== Do not's ==~~

	~~=== Depend on anything already being in $PATH ===~~

	~~Don't expect any programs to be available, not even GNU coreutils.~~

	~~Start the services program using a full path and if you need to write a script then set PATH there.~~

	~~Setting a $PATH with a shell script:~~
	~~<syntaxHighlight lang=nix>~~
	{
	~~process.argv = [~~
	~~(pkgs.writeShellScript "foo.sh" ''~~
	~~PATH="${lib.makeBinPath [ pkgs.foo pkgs.bar pkgs.coreutils ]}"~~

	~~mkdir /var/lib/foo~~
	~~foo …~~
	~~'')~~
	];
	}
	~~</syntaxHighlight>~~

	~~Or set PATH without a script using [[execline]]:~~
	~~<syntaxHighlight lang=nix>~~
	{
	~~process.argv = [~~
	~~"${pkgs.execline}/bin/export" "PATH" (lib.makeBinPath [ pkgs.foo pkgs.bar ])~~
	~~"foo" "…"~~
	];
	}
	~~</syntaxHighlight>~~

	~~== Research Topics ==~~

	~~=== "One-shot" services ===~~
	~~Some services run to completion and should not be restarted.~~

	~~Should these services we be wrapped in scripts that never return?~~

	~~=== Secrets management ===~~

	~~How to load secrets without depending on specific service managers?~~

	~~=== User management ===~~

	~~How to create new users?~~

	~~=== Security hardening ===~~

	~~Best practices for privilege de-escalation?~~

	~~=== Intra-service dependencies ===~~

	~~How should dependencies within a collection of services be expressed?~~

	~~[[Category:NixOS]]~~

Klinger: Category:NixOS

2025-08-17T13:35:48Z

Category:NixOS

← Older revision		Revision as of 13:35, 17 August 2025
Line 61:		Line 61:

	How should dependencies within a collection of services be expressed?		How should dependencies within a collection of services be expressed?

			[[Category:NixOS]]

Ehmry: /* Do not's */ $PATH

2025-08-05T21:07:36Z

Do not's: $PATH

@@ Line 7: / Line 7: @@
 == Do's ==
-== Do not Do's ==
+== Do not's ==
 == Research Topics ==

Ehmry: /* Research Topics */ Intra-service dependencies

2025-08-05T20:52:34Z

Research Topics: Intra-service dependencies

← Older revision		Revision as of 20:52, 5 August 2025
Line 27:		Line 27:

	Best practices for privilege de-escalation?		Best practices for privilege de-escalation?

			=== Intra-service dependencies ===

			How should dependencies within a collection of services be expressed?

Ehmry: Draft

2025-08-05T14:38:26Z

Draft

New page

Modular services are an experimental feature added to NixOS between the 25.05 and 25.11 releases.

For official documentation see the [https://nixos.org/manual/nixos/unstable/#modular-services NixOS Manual].

This page exists to used to collect experiences and recommendations for using this feature that would not fit well in the NixOS manual.

== Do's ==

== Do not Do's ==

== Research Topics ==

=== "One-shot" services ===
Some services run to completion and should not be restarted.

Should these services we be wrapped in scripts that never return?

=== Secrets management ===

How to load secrets without depending on specific service managers?

=== User management ===

How to create new users?

=== Security hardening ===

Best practices for privilege de-escalation?