| 13 May 2024 |
 @tc424:glasgow.social | Need to add NATS to my ever growing "things to check out" list | 17:49:17 |
 jkachmar | bento too, as far as pull-based deploy systems go | 18:21:12 |
|  DolceTriade joined the room. | 18:34:18 |
| DolceTriade | attic has been rock solid for me at work | 18:37:14 |
| DolceTriade | I run it on k8s with an https proxy in front to integrate with our existing atuh | 18:37:46 |
| DolceTriade | * I run it on k8s with an https proxy in front to integrate with our existing auth | 18:37:48 |
| DolceTriade | * I run it on k8s with an https proxy in front to integrate with our existing auth (sqlite + filesystem storage) | 18:38:00 |
|  Paddi ⚡️ joined the room. | 19:01:22 |
 danielle | In reply to @tc424:glasgow.social
Need to add NATS to my ever growing "things to check out" list I've been using nats a bit lately and it's pretty solid | 19:12:33 |
 raitobezarius | In reply to @charles:computer.surgery
"write a binary cache" is on my to do list you could also just use tvix or make it a thing in lix | 19:13:23 |
| raitobezarius | i think the binary cache impl should be more or less very sibling to the nix impl | 19:13:41 |
 Charles | not sure what you mean | 19:13:43 |
| raitobezarius | I think most of the features of a binary cache should be in a Nix implementation | 19:14:47 |
| raitobezarius | And then you can carve out various frontends / slight customizations on the top of it IMHO | 19:15:13 |
| danielle | In reply to @raitobezarius:matrix.org
I think most of the features of a binary cache should be in a Nix implementation only if you want your storage and your logic to be the same thing tho | 19:15:37 |
| raitobezarius | Ideally, I'd like to see a way to expose any store as a binary cache in frictionless way | 19:15:40 |
| raitobezarius | In reply to @danielle:fairydust.space
only if you want your storage and your logic to be the same thing tho Your logic can be added on the top IMHO | 19:16:10 |
| raitobezarius | Like if you want authnz, auth, etc. There should be a way to compose existing tools? | 19:16:27 |
 Qyriad | technically a binary cache can take multiple forms; at least one of them should be built in to Nix | 19:16:43 |
| raitobezarius | (generally, I'd like to see the concept of cache combinators) | 19:16:44 |
 samrose | If there is anything people can do to help that are not part of the core team, please let us know. | 19:19:50 |
| raitobezarius | to expand on my thoughts, indeed, binary cache means so many things, I think what would be interesting is:
-
nix has interesting and strong store backends: filesystem, S3, etc.
-
each one of them can be exposed on a reasonable protocol (HTTP/3, etc. whatever) using nix itself
-
nix can handle certain operations by itself which are reasonable: signing store paths (via PKCS#11 or local signing stuff), etc.
-
deduplication should be fundamental & baked-in
-
multi-tenancy should ideally be just multiple nix stores (maybe they can share blocks or something whatever)
-
you can bring your own reverse proxy for auth, authnz based on your "usecase" logic
-
etc.
| 19:20:41 |
| raitobezarius | obviously, you can run a S3 binary cache without nix being around | 19:21:04 |
| raitobezarius | In reply to @samrose:matrix.org
If there is anything people can do to help that are not part of the core team, please let us know. I recommend looking at https://git.lix.systems/lix-project/lix/issues?q=&type=all&state=open&labels=154&milestone=0&assignee=0&poster=0 | 19:21:28 |
| Qyriad | In reply to @samrose:matrix.org
If there is anything people can do to help that are not part of the core team, please let us know. anyone is welcome to contribute! we have a meeting being planned to work out proper governance structure Soon™️ so the "core team" at least as it is right now is largely an interim construct. identifying issues, writing docs or editing the wiki, or code contributions themselves are all very very welcome. on the flip side please let us know if there's anything we can do to help onboard! | 19:22:26 |
| raitobezarius | In reply to @raitobezarius:matrix.org
to expand on my thoughts, indeed, binary cache means so many things, I think what would be interesting is:
-
nix has interesting and strong store backends: filesystem, S3, etc.
-
each one of them can be exposed on a reasonable protocol (HTTP/3, etc. whatever) using nix itself
-
nix can handle certain operations by itself which are reasonable: signing store paths (via PKCS#11 or local signing stuff), etc.
-
deduplication should be fundamental & baked-in
-
multi-tenancy should ideally be just multiple nix stores (maybe they can share blocks or something whatever)
-
you can bring your own reverse proxy for auth, authnz based on your "usecase" logic
-
etc.
(and maybe let me add that i'd like it to be easy to make super-stores by composing a list of stores with any URI format) | 19:22:28 |
|  aria (she/it) changed their display name from aria to aria (she/it). | 19:38:17 |
| jkachmar | In reply to @raitobezarius:matrix.org
i think the binary cache impl should be more or less very sibling to the nix impl this is sort of what the tvix approach is, right?
the store should be a defined component with its own semantics and a clear interface, at which point a lot of other stuff can be implemented on top of this rather than through the current monolithic Nix binary application (e.g. binary caching, the build tool, various bits of UI on top of the store) | 19:42:33 |
| raitobezarius | correct | 19:57:44 |
|  dantefromhell joined the room. | 20:01:59 |
