foodogsquared/nixos-config
1
0
Fork 0
mirror of https://github.com/foo-dogsquared/nixos-config.git synced 2025-02-07 06:19:00 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

docs/site: make it more readable

Browse Source
This commit is contained in:
Gabriel Arazas 2024-01-06 19:15:55 +08:00
parent 8b1c513e7f
commit 65f6e90d6c
No known key found for this signature in database
GPG Key ID: ADE0C41DAB221FCC
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/content/en-US/04-nixos-modules/04-host-specific-modules/index.adoc
View File

@ -49,7 +49,7 @@ Now, we could have our host setup like in the following code.
{ config, lib, pkgs, ... } { config, lib, pkgs, ... }
{ {
# ... imports = [ ./modules ];
hosts.$HOSTNAME.services = { hosts.$HOSTNAME.services = {
# Essential services. # Essential services.
@ -66,7 +66,7 @@ Now, we could have our host setup like in the following code.
---- ----
You could even structure it further by combining all of the essential services into a module, say in `modules/core-services.nix` and enable them in a switch with `hosts.$HOSTNAME.core-services.enable`. You could even structure it further by combining all of the essential services into a module, say in `modules/core-services.nix` and enable them in a switch with `hosts.$HOSTNAME.core-services.enable`.
The possibilities are only limited in how you imagine. The possibilities are only limited in your imagination.
[chat, Ezran, state=curious, role=reversed] [chat, Ezran, state=curious, role=reversed]
==== ====

6
docs/content/en-US/05-home-manager/index.adoc
View File

@ -31,18 +31,18 @@ On the host configuration, you can then import it like so.
[source, nix] [source, nix]
---- ----
{ config, lib, pkgs, ... }: { { config, lib, pkgs, ... }: {
imports = [ (lib.getUser "nixos" "plover") ] imports = [ (lib.private.getUser "nixos" "plover") ]
} }
---- ----
But creating a dedicated NixOS user onto a file then importing the module just to use a home-manager is more of a hassle. But creating a dedicated NixOS user onto a file then importing the module just to use a home-manager is more of a hassle.
It shouldn't require much boilerplate. It shouldn't require much boilerplate.
This is why this NixOS config has created a function for it: `mapHomeManagerUser`. This is why this project has created a function for it: `mapHomeManagerUser`.
.An example of how to use it .An example of how to use it
[source, nix] [source, nix]
---- ----
lib.mapHomeManagerUser "foo-dogsquared" { lib.private.mapHomeManagerUser "foo-dogsquared" {
extraGroups = [ extraGroups = [
"adbusers" "adbusers"
"wheel" "wheel"