l4.pm
auto-reconnecting jetstream proxy
1# jetstream-proxy
2
3auto-reconnecting jetstream proxy with a default pool that should work
4
5used internally for my own projects already
6
7NOTES:
8- this should run as close to your infrastructure as possible as the proxy
9 attempts to find the best jetstream for you. you then
10 would connect to `ws://localhost:<port>/subscribe` on your app
11- **no cursor support.** since there will be multiple jetstream upstreams that
12 run at separate cursor timelines, it would be pretty hard to rewrite cursors
13 in such a way that everything works. if your application relies on cursors,
14 then it's probably best for your application to deal with multi-upstream support.
15
16## how
17
18```
19git clone https://tangled.org/@l4.pm/jetstream-proxy
20cd jetstream-proxy
21go build
22env PORT=6666 ./jetstream-proxy
23```
24
25or if youre epic and awesome
26
27```
28docker build -t jetstream-proxy .
29```