!CcTBuBritXGywOEGWJ:matrix.org

NixOS Binary Cache Self-Hosting

162 Members
About how to host a very large-scale binary cache and more55 Servers

Load older messages


SenderMessageTime
19 May 2024
@thubrecht:matrix.orgthubrechtWhat you really need is the s3_api.root_domain in the garage settings14:02:20
@hexa:lossy.networkhexaok, that is what I had all the time14:02:37
@thubrecht:matrix.orgthubrechtSorry....14:02:53
@thubrecht:matrix.orgthubrechtBut then I don't know why it doesn't work14:03:19
@hexa:lossy.networkhexano worries14:03:22
@hexa:lossy.networkhexahm ok, it is pushing stuff14:13:29
@hexa:lossy.networkhexaseems like dns is my enemy today14:13:34
@charles:computer.surgeryCharles
In reply to @hexa:lossy.network
I'm currently running into lots of dispatch failures
Hmm not sure what you mean by that
15:03:31
@charles:computer.surgeryCharlesIf you want to reference my config: https://gitlab.computer.surgery/charles/servy-fleet/-/tree/main/config?ref_type=heads the attic and garage directories are relevant15:04:58
@charles:computer.surgeryCharlesSince writing this nonsense https://gitlab.computer.surgery/matrix/grapevine-fork/-/blob/main/bin/nix-build-and-cache?ref_type=heads attic has been a lot more useful for me15:06:05
@charles:computer.surgeryCharlesI might try building this functionality into the attic client, since it already has the ability to compute closures15:06:36
@charles:computer.surgeryCharlesAlso I think that when using garage you should disable attic's chunking, because garage does that already15:08:37
@charles:computer.surgeryCharles

My three biggest gripes with attic right now are:

  • Sometimes the connection randomly dies while pushing
  • It's impossible to revoke authentication tokens
  • There's no built in way to do what the above script does
15:10:31
@charles:computer.surgeryCharlesI haven't experienced the first one in a while though15:11:01
@charles:computer.surgeryCharles

Maybe also:

  • It's not in nixpkgs and it doesn't have its own binary cache so you often have to build it yourself
15:11:46
@hexa:lossy.networkhexaI mentioned you becuase I found your issue on the attic repo15:12:07
@hexa:lossy.networkhexa * I mentioned you because I found your issue on the attic repo15:12:14
@hexa:lossy.networkhexanow running into15:12:23
@hexa:lossy.networkhexa

❌ yn5nd583m3ynfwkg19dc9vxfi5f7bnzy-systemd-254.10: HTTP 413 Payload Too Large

15:12:26
@hexa:lossy.networkhexanow what limits the payload size 🤔15:13:05
@charles:computer.surgeryCharlesI assume you're using NGINX?15:13:06
@hexa:lossy.networkhexaoh right15:13:10
@charles:computer.surgeryCharlesSet client max body to 0 lol15:13:25
@hexa:lossy.networkhexa🤡15:13:42
@julienmalka:matrix.orgJulien
In reply to @charles:computer.surgery

Maybe also:

  • It's not in nixpkgs and it doesn't have its own binary cache so you often have to build it yourself
It's in nixpkgs now iirc
15:13:53
@charles:computer.surgeryCharlesOh it is, nice15:14:32
@charles:computer.surgeryCharles
In reply to @hexa:lossy.network
I mentioned you because I found your issue on the attic repo
Oh I haven't hit https://github.com/zhaofengli/attic/issues/108 in a long time, no idea what changed l
15:15:15
@charles:computer.surgeryCharles* Oh I haven't hit https://github.com/zhaofengli/attic/issues/108 in a long time, no idea what changed lol15:15:20
@hexa:lossy.networkhexaI think it is the error you get for all kinds of S3 connection issues15:15:35
@hexa:lossy.networkhexafor me it was DNS propagation/caching15:15:40

Show newer messages


Back to Room ListRoom Version: 10