27 Mar 2024 |
| @admin:nixos.org set the room name to "NixOS Deployments". | 16:59:32 |
| Room Avatar Renderer. | 16:59:32 |
| @admin:nixos.org set the room topic to "NixOS Deployment tooling". | 16:59:33 |
| @admin:nixos.org left the room. | 16:59:38 |
28 Mar 2024 |
| Givon Washington joined the room. | 00:57:36 |
hexa | does anyone understand how [Comin}(https://discourse.nixos.org/t/comin-git-push-nixos-machines/40688) beats system.autoUpgrade for simple use cases like
system.autoUpgrade = {
enable = true;
dates = "hourly";
flake = "git+https://git.darmstadt.ccc.de/noc/builders-nix.git?ref=main";
allowReboot = true;
};
| 03:26:00 |
hexa | * does anyone understand how Comin beats system.autoUpgrade for simple use cases like
system.autoUpgrade = {
enable = true;
dates = "hourly";
flake = "git+https://git.darmstadt.ccc.de/noc/builders-nix.git?ref=main";
allowReboot = true;
};
| 03:26:09 |
hexa |
Before using comin, i have been actually using the auto-upgrade module for years! Basically, comin “just” provides more features (and a lot more are planned).
| 03:27:18 |
lewo | hexa: for simple use cases, it is not better than system.autoUpgrade . On your example, differences are: | 06:02:26 |
lewo | * hexa: for simple use cases, it is not better than system.autoUpgrade . On your example, differences are:
- comin doesn't support yet reboot
- comin doesn't allow a branch "hard reset" (currenlty this is not true when your restart comin)
| 06:03:46 |
lewo | The major features this first version of comin brings are multiple remotes and testing branches. Thes features allowed me to use comin on my laptop while i didn't find autoUpgrade suitable for this use case. | 06:07:04 |
lewo | * The major features for this first version of comin brings are multiple remotes and testing branches. Thes features allowed me to use comin on my laptop while i didn't find autoUpgrade suitable for this use case. | 07:35:04 |
| rungmc joined the room. | 18:21:38 |
| zodman set a profile picture. | 18:59:18 |
| wrycode joined the room. | 20:22:18 |
29 Mar 2024 |
| SebTM joined the room. | 03:38:41 |
| tom changed their display name from Tom to tom. | 14:44:17 |
| @eclipsed-raven:matrix.org joined the room. | 14:45:56 |
| @eclipsed-raven:matrix.org left the room. | 14:48:09 |
parallel21 | I use nixos-rebuild switch --flake... to deploy my nix config to a remote host. I am looking for a way to take a file I have "my-config.toml" and write it to the host. What's the "nix" way of doing this? Writing the file to the nix-store and then using systemd to create a symlink if I want it referenced in a specific folder | 17:32:00 |
parallel21 | * I use nixos-rebuild switch --flake... to deploy my nix config to a remote host. I am looking for a way to take a file I have "my-config.toml" and write it to the host. What's the "nix" way of doing this? Writing the file to the nix-store and then using systemd to create a symlink if I want it referenced in a specific folder? | 17:32:06 |
K900 | Yes\ | 17:32:40 |
K900 | * Yes | 17:32:43 |
K900 | Unless the folder is /etc, in which case use environment.etc | 17:32:51 |
parallel21 | Might you know of an example of this somewhere? | 17:35:02 |
K900 | What's the path? | 17:35:50 |
parallel21 | Thanks in the least for confirming my suspicion. | 17:36:19 |
parallel21 | /var/lib/rancher/k3s/server/manifests | 17:36:25 |
K900 | Use systemd.tmpfiles.rules then | 17:37:03 |
parallel21 | Like
systemd.tmpfiles.rules = [
"L+ /var/lib/rancher/k3s/server/manifests - - - - ${bootstrapFile}"
];
}```
| 17:40:50 |