We can’t do more than like 5 requests right next to each other, so let’s handle the timeout they request. This kinda destroys search speeds for large search results, so we might have to filter out collections somehow, or do something smarter like schedule things out and show a preliminary result at one point. Change-Id: If916379eb6e19cf8e960cf7553965b338645e560 Reviewed-on: https://cl.tvl.fyi/c/depot/+/12958 Tested-by: BuildkiteCI Reviewed-by: Profpatsch <mail@profpatsch.de> |
||
|---|---|---|
| .. | ||
| services | ||
| src | ||
| .gitignore | ||
| build.ninja | ||
| default.nix | ||
| Main.hs | ||
| notes.org | ||
| README.md | ||
| server-notes.org | ||
| whatcd-resolver.cabal | ||
whatcd-resolver
To run:
ninja run-services
in one terminal (starts the background tasks)
ninja run
to start the server. It runs on 9092.
You need to be in the nix-shell in ./...
You need to set the pass key internet/redacted/api-keys/whatcd-resolver to an API key for RED.
You need to have a transmission-rpc-daemon listening on port 9091 (no auth, try ssh port forwarding lol).