feat(rust): automated deployment to fly.io #91
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
This is ready from my PoV. In the current state, the rust-peer is a general bootnode and not directly tied to any of our deployments. It does have a default to connect to our deployment but users can override that. In my opinion, this is a nice middlegroup between having this work out of the box but also being general enough to teach others how to bootstrap their own network. |
| cmd = ["/bin/sh", "-c", "set -ex; LISTEN_ADDRESS=$(getent hosts fly-global-services | cut -d' ' -f1) && rust-libp2p-webrtc-peer"] | ||
|
|
||
| [env] | ||
| EXTERNAL_ADDRESS="149.248.215.31" # TODO: Remove this in favor of an AutoNAT setup. |
There was a problem hiding this comment.
Would AutoNAT even work when deployed to Fly.io? In my experience running Kubo on fly.io, their overlay network messes with AutoNAT and results in the wrong IP, but it's been a while since I actually tried it and I didn't dive too deep.
| # | ||
|
|
||
| app = "universal-connectivity-rust-peer" | ||
| primary_region = "syd" |
There was a problem hiding this comment.
Any thoughts on moving this to Europe/US, where most users will likely be connecting from?
There was a problem hiding this comment.
Happy to, this is just the default 😅
|
The node is deployed, but I'm unable to connect to it from the browser. Here's the latest deployed multiaddr:
I get the following error |
|
Weird! It does work locally but for some reason, can't connect to the deployed one on fly.io. cc @libp2p/js-libp2p-dev |
I'd like to deploy an instance of the Rust peer to a fly.io worker everytime we merge to master. I tested this and it does work although unfortunately only for IPv4. It is a start though and perhaps fly.io will at some point support UDP + IPv6. See https://fly.io/docs/app-guides/udp-and-tcp/#udp-wont-work-over-ipv6 for details.
Currently, this is running on the free-tier and thus does not incur any costs.