mirror of
https://github.com/ryan4yin/nixos-and-flakes-book
synced 2024-09-20 14:41:59 +00:00
feat: nixos modules vs home manager
This commit is contained in:
Ryan Yin
parent
c76ee51c20
commit
c65db98b97
2 changed files with 25 additions and 11 deletions
|
|
@ -233,17 +233,25 @@ To find the options we can use in `home.nix`, referring to the following documen
|
|||
|
||||
## Home Manager vs NixOS
|
||||
|
||||
When it comes to managing software packages and configurations, you often have the choice of using either NixOS modules (`configuration.nix`) or Home Manager (`home.nix`). This poses a dilemma: **What are the differences between putting packages or configuration in NixOS modules vs Home Manager modules, and how should you decide?**
|
||||
There are many software packages or configurations that can be set up using either NixOS Modules (`configuration.nix`) or Home Manager (`home.nix`), which brings about a choice dilemma: **What is the difference between placing software packages or configuration files in NixOS Modules versus Home Manager, and how should one make a decision?**
|
||||
|
||||
First, let's understand the differences. Packages and configuration installed through NixOS modules are global to the entire system. Global configurations are typically stored in `/etc`, and globally installed packages are linked accordingly. Regardless of the user you switch to, you can access and use these packages and configurations.
|
||||
First, let's look at the differences: Software packages and configuration files installed via NixOS Modules are global to the entire system. Global configurations are usually stored in `/etc`, and system-wide installed software is accessible in any user environment.
|
||||
|
||||
On the other hand, everything installed through Home Manager is specific to the corresponding user. Once you switch to another user, those configurations and packages become unavailable.
|
||||
On the other hand, configurations and software installed via Home Manager will be linked to the respective user's Home directory. The software installed is only available in the corresponding user environment, and it becomes unusable when switched to another user.
|
||||
|
||||
Based on these characteristics, the general recommended usage is:
|
||||
|
||||
- NixOS Modules: Install system core components and other software packages or configurations needed by all users.
|
||||
- For instance, if you want a software package to continue working when you switch to the root user, or if you want a configuration to apply system-wide, you should install it using NixOS Modules.
|
||||
- Home Manager: Use Home Manager for all other configurations and software.
|
||||
|
||||
The benefits of this approach are:
|
||||
|
||||
1. Software and background services installed at the system level often run with root privileges. Avoiding unnecessary software installations at the system level can reduce the security risks of the system.
|
||||
1. Many configurations in Home Manager are universal for NixOS, macOS, and other Linux distributions. Choosing Home Manager to install software and configure systems can improve the portability of configurations.
|
||||
1. If you need multi-user support, software and configurations installed via Home Manager can better isolate different user environments, preventing configuration and software version conflicts between users.
|
||||
|
||||
Based on these characteristics, here is a general recommended approach:
|
||||
|
||||
- NixOS modules: Install core system components and other software packages/configurations required by all users.
|
||||
- For example, if you want a package to be accessible even when you switch to the root user, or if you want a configuration to take effect globally on the system, you should install it through a NixOS module.
|
||||
- Home Manager: Use Home Manager to install all other configurations and software specific to individual users.
|
||||
|
||||
## How to use packages installed by Home Manager with privileged access?
|
||||
|
||||
|
|
|
|||
|
|
@ -236,12 +236,11 @@ nix flake new example -t github:nix-community/home-manager#nixos
|
|||
|
||||
## Home Manager vs NixOS
|
||||
|
||||
有许多的软件包或者软件配置, 既可以使用 NixOS Module 配置(`configuration.nix`)，也可以使用 Home Manager 配置(`home.nix`), 这带来一个选择难题: **将软件包或者配置文件写在 NixOS Module 里还是 Homa Manager 配置里面有何区别? 该如何决策?**
|
||||
有许多的软件包或者软件配置, 既可以使用 NixOS Module 配置(`configuration.nix`)，也可以使用 Home Manager 配置(`home.nix`), 这带来一个选择难题：**将软件包或者配置文件写在 NixOS Module 里还是 Homa Manager 配置里面有何区别? 该如何决策?**
|
||||
|
||||
首先看看区别, NixOS Module 中安装的软件包跟配置文件都是整个系统全局的, 全局的配置通常会被存放在 `/etc` 中, 而全局的软件也通常被链接到全局. 不论切换到哪个用户下,
|
||||
都能正常使用该软件或配置.
|
||||
首先看看区别, NixOS Module 中安装的软件包跟配置文件都是整个系统全局的, 全局的配置通常会被存放在 `/etc` 中, 系统全局安装的软件也在任何用户环境下都可使用。
|
||||
|
||||
而 Home Manager 安装的所有东西, 都仅在对应的用户下可用, 切换到其他用户后这些配置跟软件就都失效了.
|
||||
相对的，通过 Home Manager 安装的配置项将会被链接到对应用户的 Home 目录, 其安装的软件也仅在对应的用户环境下可用, 切换到其他用户后这些配置跟软件就都用不了了。
|
||||
|
||||
根据这种特性, 一般的推荐用法是:
|
||||
|
||||
|
|
@ -249,6 +248,13 @@ nix flake new example -t github:nix-community/home-manager#nixos
|
|||
- 比如说如果你希望某个软件包能在你切换到 root 用户时仍能正常使用, 或者使某个配置能在系统全局生效, 那就得用 NixOS Module 来安装它
|
||||
- Home Manager: 其他所有的配置与软件, 都建议用 Home Manager 来安装
|
||||
|
||||
这样做的好处是：
|
||||
|
||||
1. 系统层面安装的软件与后台服务常常以 root 特权用户的身份运行，尽量避免在系统层面安装不必要的软件，可以减少系统的安全风险。
|
||||
1. Home Manager 的许多配置都可以在 NixOS, macOS 以及其他 Linux 发行版上通用，尽可能选用 Home Manager 来安装软件与配置系统，可以提高配置的可移植性。
|
||||
1. 如果你需要多用户，通过 Home Manager 安装的软件与配置，可以更好地隔离不同用户的环境，避免不同用户之间的配置与软件版本冲突。
|
||||
|
||||
|
||||
## 如何以特权身份使用 Home Manager 安装的软件包?
|
||||
|
||||
对这个问题，首先想到的一般都是直接切换到 `root` 用户, 可切换用户后，当前用户通过 `home.nix` 安装的软件包都将不可用。
|
||||
|
|
|
|||
Loading…
Reference in a new issue