| 6 Feb 2026 |
 n3tcat | hmm does Lix change how remote deployments work? I am deploying to a sever and it looks like packages are going direct from the Nix build cache to the server. When I was on Nix I'm pretty sure it would copy them to my local machine and then copy them from my local machine to the server | 02:17:54 |
 whispers [& it/fae] | there's a builders-use-substitutes (or something similar) config option which controls this behavior | 02:23:45 |
| n3tcat | wait what does that flag do | 02:24:19 |
| whispers [& it/fae] | which is better mostly depends on whether you have the server has a faster connection to your local machine or the binary cache | 02:24:21 |
| whispers [& it/fae] | wait what exactly you do you mean by deployments | 02:24:53 |
| whispers [& it/fae] | I'm referring to remote builders, which might be the wrong thing | 02:25:06 |
| n3tcat | uh well I kinda have both
I have a remote builder but I'm doing a nixos-rebuild --switch --target 1.2.3.4 or whatever it is
In this case the remote builder isn't being used I don't think | 02:25:41 |
| whispers [& it/fae] | oh i forget then. nix-copy-closure (which is used by nixos-rebuild) does have a --use-substitutes option but i dunno if lix changes that | 02:28:43 |
| whispers [& it/fae] | * oh no clue then. nix-copy-closure (which is used by nixos-rebuild) does have a --use-substitutes option but i dunno if lix changes that | 02:28:53 |
| whispers [& it/fae] | * oh no clue then. nix-copy-closure (which is used by nixos-rebuild, which has the same option) do have a --use-substitutes option but i dunno if lix changes that | 02:32:33 |
| whispers [& it/fae] | * oh no clue then. nix-copy-closure (which is used by nixos-rebuild, which has the same option) does have a --use-substitutes option but i dunno if lix changes that | 02:32:52 |
| n3tcat | it is definitely ideal if it can copy straight from the cache to the server without needing to go through my laptop | 02:34:25 |
| n3tcat | but also maybe it's just a measurement of error of some kind of my laptop | 02:34:34 |
| 13 May 2024 |
|  zrsk joined the room. | 13:37:30 |
|  dariof4 joined the room. | 14:16:05 |
|  abbe joined the room. | 14:42:22 |
 mjm | lix is now in nixos-unstable, what's the best way to use it in a NixOS config? | 15:47:41 |
 K900 | nix.package = pkgs.lix | 15:47:54 |
| K900 | Probably | 15:47:58 |
| K900 | Or just keep using the module | 15:48:02 |
 puck | you can use nix.package = pkgs.lix; if you want; but using the overlay will guarantee more updates (tho less binary cache) | 15:48:44 |
| mjm | well, the module/overlay doesn't easily support using the one from nixpkgs | 15:48:44 |
| mjm | i do want more binary cache | 15:49:21 |
| mjm | yeah i guess i'll just do nix.package then | 15:50:43 |
 raitobezarius | to have binary cache and HEAD, we will probably need to track the channels and bolt a lix on there and rebuild with our own CI then push in our binary cache | 17:33:17 |
 Charles | What's lix using as its binary cache? Attic? | 17:34:36 |
|  Arian left the room. | 17:37:44 |
 @tc424:glasgow.social | Last I heard they were using garage as the back end, and think about attic | 17:39:11 |
| @tc424:glasgow.social | I don't know if that means they're just pushing directly into garage's s3 interface for the moment | 17:39:36 |
| @tc424:glasgow.social | * Last I heard they were using garage as the back end, and thinking about attic | 17:39:57 |
