Document using deploy-rs to deploy home-manager
This commit is contained in:
parent
65db5d30ae
commit
89b3cf78fd
1 changed files with 27 additions and 0 deletions
|
@ -45,5 +45,32 @@ deploy '.#hostName' --hostname host.example.com
|
||||||
|
|
||||||
> ##### _Note:_
|
> ##### _Note:_
|
||||||
> Your user will need **passwordless** sudo access
|
> Your user will need **passwordless** sudo access
|
||||||
|
### Home Manager
|
||||||
|
|
||||||
|
Digga's `lib.mkDeployNodes` provides only `system` profile.
|
||||||
|
In order to deploy your `home-manager` configuration you should provide additional profile(s) to deploy-rs config:
|
||||||
|
```nix
|
||||||
|
# Initially, this line looks like this: deploy.nodes = digga.lib.mkDeployNodes self.nixosConfigurations { };
|
||||||
|
deploy.nodes = digga.lib.mkDeployNodes self.nixosConfigurations
|
||||||
|
{
|
||||||
|
<HOSTNAME> = {
|
||||||
|
profilesOrder = [ "system" "<HM_PROFILE>" "<ANOTHER_HM_PROFILE>"];
|
||||||
|
profiles.<HM_PROFILE> = {
|
||||||
|
user = "<YOUR_USERNAME>";
|
||||||
|
path = deploy.lib.x86_64-linux.activate.home-manager self.homeConfigurationsPortable.x86_64-linux.<YOUR_USERNAME>;
|
||||||
|
};
|
||||||
|
profiles.<ANOTHER_HM_PROFILE> = {
|
||||||
|
user = "<ANOTHER_USERNAME>";
|
||||||
|
path = deploy.lib.x86_64-linux.activate.home-manager self.homeConfigurationsPortable.x86_64-linux.<ANOTHER_USERNAME>;
|
||||||
|
};
|
||||||
|
};
|
||||||
|
};
|
||||||
|
```
|
||||||
|
|
||||||
|
Substitute `<HOSTNAME>`, `<HM_PROFILE>` and `<YOUR_USERNAME>` placeholders (omitting the `<>`).
|
||||||
|
|
||||||
|
`<ANOTHER_HM_PROFILE>` is there to illustrate deploying multiple `home-manager` configurations. Either substitute those as well,
|
||||||
|
or remove them altogether. Don't forget the `profileOrder` variable.
|
||||||
|
|
||||||
|
|
||||||
[d-rs]: https://github.com/serokell/deploy-rs
|
[d-rs]: https://github.com/serokell/deploy-rs
|
||||||
|
|
Loading…
Reference in a new issue