jetstream-proxy #

auto-reconnecting jetstream proxy with a default pool that should work

used internally for my own projects already

NOTES:

• this should run as close to your infrastructure as possible as the proxy attempts to find the best jetstream for you. you then would connect to ws://localhost:<port>/subscribe on your app
• no cursor support. since there will be multiple jetstream upstreams that run at separate cursor timelines, it would be pretty hard to rewrite cursors in such a way that everything works. if your application relies on cursors, then it's probably best for your application to deal with multi-upstream support.

how #

git clone https://tangled.org/@l4.pm/jetstream-proxy
cd jetstream-proxy
go build
env PORT=6666 ./jetstream-proxy

or if youre epic and awesome

docker build -t jetstream-proxy .