| 5 Sep 2021 |
 edrex | I'm currently trying to get some method of remote builds from my non-nixos workstation working for my flake-based nixosConfigurations, and am hitting several issues with both using nixos-rebuild and deploy-rs | 21:01:42 |
| edrex | this is where I'm at with nixos-rebuild: https://clbin.com/lXZcx | 21:02:46 |
| edrex | and with deploy-rs: https://clbin.com/Aw7vk (although i somehow managed to get that output from a remote nixos-rebuild at some point as well iirc) | 21:04:44 |
| edrex | the grub assertion doesn't fail with a local nixos-rebuild | 21:05:36 |
| edrex | (i'm using a pi with extlinux bootloader) | 21:06:00 |
| edrex | i think grahamc (he/him) hit the same or similar nixos-rebuild issue last month. | 21:07:56 |
| edrex | i think what makes me special is a) nixos-rebuild on non-nixos system (seems like that's condition for the nixos-rebuild error) and b) amd64 -> aarch64 (guessing that's what leads to the grub assertion) | 21:10:15 |
| edrex | In reply to @blaggacao:matrix.org
But no guarantees that it fits any given rabbithole at any given moment. But it's a nice place to get together on some standardization. i'm totally sold on the virtues of community-based config, but i would greatly prefer a library/mixin/bazaar approach (like ala-carte with a bunch of flake vendors) over the single-vendor template-based approach used by eg spacemacs and doom. I don't like helpers that require me to clear my table and start over. | 21:28:32 |
| edrex | fewer layers of abstraction = better. | 21:29:22 |
 David Arnold (blaggacao) | I'm afraid currently deploy-rs seems not to be the right tool for remote building. | 21:29:43 |
| David Arnold (blaggacao) | It probably can and (I predict) will be expanded into that field of use cases. | 21:30:36 |
| edrex | reading the label on the tin it seems like that's what it's mean for, yes? | 21:31:12 |
| edrex | deploy.nodes.hostname, ssh user/port details, etc | 21:31:55 |
| David Arnold (blaggacao) | Not building. But (advanced) nix --store uris might make that a simple improvment undertaking although not yet anywhere documented. | 21:32:23 |
| edrex | oh, I'm a little fuzzy on where the actual builds are happening with each of these tools | 21:33:17 |
| David Arnold (blaggacao) | In reply to @edrex:matrix.org
i'm totally sold on the virtues of community-based config, but i would greatly prefer a library/mixin/bazaar approach (like ala-carte with a bunch of flake vendors) over the single-vendor template-based approach used by eg spacemacs and doom. I don't like helpers that require me to clear my table and start over. The flipside is requireing (human) helpers to clear their desk 😁 - other than that fundamental concern, I'm with you! | 21:33:54 |
| David Arnold (blaggacao) | 😃 | 21:34:19 |
| edrex | it makes sense that the builds are still happening on the target (i guess the "closure" of the derivation is sent to the target? not sure if i'm using the right terms) | 21:34:33 |
| edrex | I'm fine with that, I just want to be able to trigger deploys from a local config dir on my workstation | 21:35:11 |
| edrex | In reply to @blaggacao:matrix.org
The flipside is requireing (human) helpers to clear their desk 😁 - other than that fundamental concern, I'm with you! I don't think I caught your meaning. Distracting/demanding support requests to contributors/maintainers? | 21:37:53 |
| David Arnold (blaggacao) | Btw, I don't want to insist too much, but I have a sense digga is the library approach you're maybe looking for, but that's a bit off topic. | 22:42:49 |
| David Arnold (blaggacao) | deploy-rs builds locally and deploys remotely, whereas for the deployment part, "local" could be a special case of "remote". | 22:43:44 |
| David Arnold (blaggacao) | * `deploy-rs` builds locally and deploys remotely, whereas for the deployment part, "local" could be a special case of "remote". (Deployment involves copying the closure to the target or substituing files it from a cache) | 22:44:54 |
| David Arnold (blaggacao) | * `deploy-rs` builds locally and deploys remotely, whereas for the deployment part, "local" could be a special case of "remote". Deployment thereby involves copying the closure to the target or substituing files it from a cache. | 22:45:25 |
| David Arnold (blaggacao) | * Btw, I don't want to insist too much, but I have a sense `digga` is the library approach you're maybe looking for, but that's a bit off topic. If not for usage, though so maybe for inspiration/understanding. | 22:46:26 |
| David Arnold (blaggacao) | * Btw, I don't want to insist too much, but I have a sense `digga` is the library approach you're maybe looking for, but that's a bit off topic. If not for usage, though so maybe for inspiration/understanding you can add it to your resources. | 22:46:54 |
| David Arnold (blaggacao) | * Btw, I don't want to insist too much, but I have a sense `digga` is the library approach you're maybe looking for, but that's a bit off topic. If not for usage, though so maybe for inspiration/understanding you may add it to your resources. | 22:47:05 |
| David Arnold (blaggacao) | In reply to @edrex:matrix.org
I don't think I caught your meaning. Distracting/demanding support requests to contributors/maintainers? Yeah, the great power of nix leads to chaotic adoption patterns. And sometimes, I find myself spending unreasonable amounts of time loading foreign-to-me patterns into context without gaining any functionality. | 22:49:50 |
| David Arnold (blaggacao) | * Yeah, the great power of nix leads to somewhat chaotic adoption patterns. And sometimes, I find myself spending unreasonable amounts of time loading foreign-to-me patterns into context without gaining any functionality. | 22:50:07 |
| David Arnold (blaggacao) | * Yeah, the great power of nix leads to somewhat chaotic adoption patterns. And sometimes, I find myself spending unreasonable amounts of time loading foreign-to-me patterns into context without gaining any functionality or improvenent | 22:50:38 |
