home-manager/README.md

268 lines
6.9 KiB
Markdown
Raw Normal View History

2017-01-14 13:04:57 +01:00
Home Manager using Nix
======================
This project provides a basic system for managing a user environment
using the [Nix][] package manager together with the Nix libraries
found in [Nixpkgs][]. Before attempting to use Home Manager please
read the warning below.
Words of warning
----------------
This project is under development. I personally use it to manage
2017-01-14 13:04:57 +01:00
several user configurations but it may fail catastrophically for you.
So beware!
In some cases Home Manager cannot detect whether it will overwrite a
previous manual configuration. For example, the Gnome Terminal module
will write to your dconf store and cannot tell whether a configuration
that it is about to be overwrite was from a previous Home Manager
generation or from manual configuration.
2017-01-14 13:04:57 +01:00
Home Manager targets [NixOS][] unstable and NixOS version 17.09 (the
current stable version), it may or may not work on other Linux
distributions and NixOS versions.
2017-04-01 23:05:36 +02:00
Also, the `home-manager` tool does not explicitly support rollbacks at
the moment so if your home directory gets messed up you'll have to fix
it yourself (you can attempt to run the activation script for the
2017-04-01 23:05:36 +02:00
desired generation).
2017-01-14 13:04:57 +01:00
Now when your expectations have been built up and you are eager to try
all this out you can go ahead and read the rest of this text.
Installation
------------
Currently the easiest way to install Home Manager is as follows:
1. Make sure you have a working Nix installation. If you are not
using NixOS then you may here have to run
2017-01-14 13:04:57 +01:00
```console
$ mkdir -m 0755 -p /nix/var/nix/{profiles,gcroots}/per-user/$USER
```
since Home Manager uses these directories to manage your profile
generations. On NixOS these should already be available.
Also make sure that your user is able to build and install Nix
packages. For example, you should be able to successfully run a
command like `nix-instantiate '<nixpkgs>' -A hello`. For a
multi-user install of Nix this means that your user must be
covered by the [`allowed-users`][nixAllowedUsers] Nix option. On
NixOS you can control this option using the
[`nix.allowedUsers`][nixosAllowedUsers] system option.
2. Assign a temporary variable holding the URL to the appropriate
archive. Typically this is
2017-01-14 13:04:57 +01:00
```console
$ HM_PATH=https://github.com/rycee/home-manager/archive/master.tar.gz
2017-01-14 13:04:57 +01:00
```
or
```console
$ HM_PATH=https://github.com/rycee/home-manager/archive/release-17.09.tar.gz
```
depending on whether you follow Nixpkgs unstable or version 17.09.
3. Create an initial Home Manager configuration file:
```console
$ cat > ~/.config/nixpkgs/home.nix <<EOF
{
programs.home-manager.enable = true;
programs.home-manager.path = $HM_PATH;
}
EOF
2017-01-14 13:04:57 +01:00
```
4. Install Home Manager and create the first Home Manager generation:
2017-01-14 13:04:57 +01:00
```console
$ nix-shell $HM_PATH -A install
2017-01-14 13:04:57 +01:00
```
Home Manager should now be active and available in your user
environment.
5. If you do not plan on having Home Manager manage your shell
configuration then you must source the
```
"$HOME/.nix-profile/etc/profile.d/hm-session-vars.sh"
```
file in your shell configuration. Unfortunately, we currently only
support POSIX.2-like shells such as [Bash][] or [Z shell][].
For example, if you use Bash then add
```bash
. "$HOME/.nix-profile/etc/profile.d/hm-session-vars.sh"
```
to your `~/.profile` file.
Note, because the `HM_PATH` variable above points to the live Home
Manager repository you will automatically get updates whenever you
build a new generation. If you dislike automatic updates then perform
2017-11-29 23:53:49 +01:00
a Git clone of the desired branch and instead do the above steps with
`HM_PATH` set to the _absolute path_ of your clone.
2017-01-14 13:04:57 +01:00
Usage
-----
Home Manager is typically managed through the `home-manager` tool.
This tool can, for example, apply configurations to your home
2017-01-14 13:04:57 +01:00
directory, list user packages installed by the tool, and list the
configuration generations.
As an example, let us expand the initial configuration file from the
installation above to install the htop and fortune packages, install
2017-11-13 00:38:26 +01:00
Emacs with a few extra packages enabled, install Firefox with the
IcedTea plugin enabled, and enable the user gpg-agent service.
2017-01-14 13:04:57 +01:00
To satisfy the above setup we should elaborate the
`~/.config/nixpkgs/home.nix` file as follows:
2017-01-14 13:04:57 +01:00
```nix
2017-02-04 19:56:44 +01:00
{ pkgs, ... }:
2017-01-14 13:04:57 +01:00
{
home.packages = [
pkgs.htop
pkgs.fortune
];
programs.emacs = {
enable = true;
extraPackages = epkgs: [
epkgs.nix-mode
epkgs.magit
];
};
programs.firefox = {
enable = true;
2017-11-13 00:38:26 +01:00
enableIcedTea = true;
2017-01-14 13:04:57 +01:00
};
services.gpg-agent = {
enable = true;
defaultCacheTtl = 1800;
enableSshSupport = true;
};
programs.home-manager = {
enable = true;
path = "…";
};
2017-01-14 13:04:57 +01:00
}
```
To activate this configuration you can then run
```console
$ home-manager switch
2017-01-14 13:04:57 +01:00
```
or if you are not feeling so lucky,
```console
$ home-manager build
```
which will create a `result` link to a directory containing an
activation script and the generated home directory files.
To see available configuration options with descriptions and usage
examples run
2017-09-21 10:23:23 +02:00
```console
2017-09-21 10:23:23 +02:00
$ man home-configuration.nix
```
2017-05-17 23:26:16 +02:00
Keeping your ~ safe from harm
-----------------------------
2017-10-04 00:24:59 +02:00
To configure programs and services Home Manager must write various
things to your home directory. To prevent overwriting any existing
files when switching to a new generation, Home Manager will attempt to
detect collisions between existing files and generated files. If any
such collision is detected the activation will terminate before
changing anything on your computer.
For example, suppose you have a wonderful, painstakingly created
`~/.gitconfig` and add
```nix
{
# …
programs.git = {
enable = true;
userName = "Jane Doe";
userEmail = "jane.doe@example.org";
};
# …
}
```
to your configuration. Attempting to switch to the generation will
then result in
```console
$ home-manager switch
Activating checkLinkTargets
Existing file '/home/jdoe/.gitconfig' is in the way
Please move the above files and try again
```
Graphical services
------------------
Home Manager includes a number of services intended to run in a
graphical session, for example `xscreensaver` and `dunst`.
Unfortunately, such services will not be started automatically unless
you let Home Manager start your X session. That is, you have something
like
```nix
{
# …
services.xserver.enable = true;
# …
}
```
in your system configuration and
```nix
{
# …
xsession.enable = true;
2017-10-04 00:24:59 +02:00
xsession.windowManager.command = "…";
# …
}
```
in your Home Manager configuration.
[Bash]: https://www.gnu.org/software/bash/
2017-01-14 13:04:57 +01:00
[Nix]: https://nixos.org/nix/
[NixOS]: https://nixos.org/
[Nixpkgs]: https://nixos.org/nixpkgs/
[nixAllowedUsers]: https://nixos.org/nix/manual/#conf-allowed-users
[nixosAllowedUsers]: https://nixos.org/nixos/manual/options.html#opt-nix.allowedUsers
[Z shell]: http://zsh.sourceforge.net/