superconfig/2configs/services/flix/ at 5933ac1c250a1df55253881bcbe00443d79b552d · hermes.pds.lassul.us/superconfig · Tangled

hermes.pds.lassul.us / superconfig

forked from lass.pds.lassul.us/superconfig

0

This repository has no description

0

superconfig / 2configs / services / flix

5 files

at 5933ac1c250a1df55253881bcbe00443d79b552d

lassulus services.flix: pin flix upstream to yellow retiolum ip4 7w ago

container-host.nix

services.flix: pin flix upstream to yellow retiolum ip4 jellyfin only listens on IPv4, but yellow.r also resolves to its retiolum AAAA. nginx round-robined both addresses, so requests hitting the v6 upstream failed and poisoned the upstream group, causing intermittent 502 'no live upstreams' on flix.lassul.us. Also drop the stale duplicate flix vhost from container-host.nix.

1 month ago

flix: skip cheetah3 metadata check (ct3 dist vs cheetah3 pname breaks sabnzbd build)

2 months ago

flix/ipfs: drop pin-add lock (concurrent --nocopy is idempotent) The flock around `ipfs add --nocopy` in the watcher and reconcile sweep guarded against a corruption that was assumed, never observed: it was added defensively alongside the reconcile sweep and never exercised (the MFS deadlock masked it). Tested it directly on kubo 0.40.1: 10 trials of two concurrent `ipfs add --nocopy --pin` on the same 16MB file, no lock. Every trial produced the same CID, a complete DAG (refs -r), and byte-identical content (cat | sha256sum). Concurrent same-file --nocopy adds are idempotent, so the lock guards nothing -- remove it.

3 months ago

ipfs.lassul.us: pin service only calculates hash, never pins

4 months ago

services.flix: pin flix upstream to yellow retiolum ip4 jellyfin only listens on IPv4, but yellow.r also resolves to its retiolum AAAA. nginx round-robined both addresses, so requests hitting the v6 upstream failed and poisoned the upstream group, causing intermittent 502 'no live upstreams' on flix.lassul.us. Also drop the stale duplicate flix vhost from container-host.nix.

1 month ago