Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

modularity: Document the ability to use non-files in imports #50503

Merged
merged 2 commits into from
Nov 28, 2018
Merged

modularity: Document the ability to use non-files in imports #50503

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2722911
modularity: Document the ability to use non-files in imports
Baughn Nov 17, 2018
9c1a6e6
Update nixos/doc/manual/configuration/modularity.xml
markuskowa Nov 27, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions nixos/doc/manual/configuration/modularity.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -127,4 +127,23 @@ nix-repl> map (x: x.hostName) config.<xref linkend="opt-services.httpd.virtualHo
[ "example.org" "example.gov" ]
</screen>
</para>

<para>
While abstracting your configuration, you may find it useful to generate
modules using code, instead of writing files. The example
below would have the same effect as importing a file which sets those
options.
<screen>
{ config, pkgs, ... }:

let netConfig = { hostName }: {
networking.hostName = hostName;
networking.useDHCP = false;
};

in

{ imports = [ (netConfig "nixos.localdomain") ]; }
</screen>
</para>
</section>