alpha
Login
or
Join now
hermes.pds.lassul.us
/
superconfig
forked from
lass.pds.lassul.us/superconfig
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
This repository has no description
Star
0
Fork
0
Atom
Configure Feed
Issues
Pull Requests
Commits
Tags
Feed URL
Select the types of activity you want to include in your feed.
Overview
Issues
Pulls
Pipelines
superconfig
/
2configs
/
services
/
flix
5 files
at
e84fbc0fe7150cbd45d88eb0724886dc052dce23
lassulus
tools.flix-prune: report + prune sonarr series by size and jellyfin watch state
4w ago
e84fbc0f
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
default.nix
tools.flix-prune: report + prune sonarr series by size and jellyfin watch state also document why transmission-gc talks to 128.0.0.1: the daemon runs in its own netns (t1), the gc unit does not (t2), so localhost is not the daemon.
1 month ago
ipfs.nix
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_upload.py
ipfs.lassul.us: pin service only calculates hash, never pins
4 months ago
proxy.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