foodogsquared/nixos-config
1
0
Fork 0
mirror of https://github.com/foo-dogsquared/nixos-config.git synced 2025-01-31 04:58:01 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
a8820aae0f
nixos-config/users
History
Gabriel Arazas c3acfe9936 users/foo-dogsquared: remove mopidy-spotify 
As the error notified, Spotify will remove third-party support, leaving
out packages like this in the dust, being unusable. :(
2022-06-12 13:45:05 +08:00
..
home-manager/foo-dogsquared users/foo-dogsquared: remove mopidy-spotify 2022-06-12 13:45:05 +08:00
nixos/nixos Modularize nixos user 2022-02-05 18:52:19 +08:00
README.adoc Update documentation 2021-12-21 14:29:27 +08:00

README.adoc

This is where user-specific configurations comes in. Similar to modules, the top-level of this directory contains users for various types (e.g., home-manager, NixOS) where it contains individual users for that type.

Take note of the following structure:

users/
├── home-manager/
│   ├── foo-dogsquared/
│   ├── harepoint/
│   └── polski/
├── nixos/
│   ├── foo-dogsquared/
│   ├── harepoint/
│   ├── polski/
│   └── vmguest/
└── README.adoc

It doesn’t require to have users to be present for all types. There are conventions for setting in each user type.

  • For NixOS user configuration, it is expect to only have one user with their respective user-specific configuration. This includes user-specific packages, home-manager-specific configuration (even importing them from ./home-manager users), and so forth. If you want to set users from the host, see Host-specific configurations for more details.

  • home-manager users are just home-manager configurations (i.e., $XDG_CONFIG_HOME/nix/home.nix). That’s pretty much it.