I like fly, but I think the only fly feature being used here is the ability to turn the machine off and have it automatically come back in when an ssh is next attempted?
Author here: It’s fun because I’ve also gotten comments saying there’s “too much” fly.io marketing in that article, when clearly your question indicates that there wasn’t enough!
Halkcyon is right that the fly thing is an excuse to mess with some Rust, but if I had to list the “features” used:
The fact that none of this seems particularly surprising may actually be a positive - it’s boring because it all just works fine the first time.
To re-iterate: my focus there was on Rust: I’ve always wanted to play with io-uring and to show a small example of what eBPF can do, and now it’s done. The example I’ve picked is kinda wonky (although I’m happy with it for day-to-day work) but I can see some folks reading the article and going “wait we could use this to have a geographically-distributed eBPF-powered firewall in front of our application” and that makes a lot more sense, for example.
Although this is too much but it wouldn’t be fun if it did not go all the way.
In anycase, thank you so much for all the stuff that you do :)
The focus of the article at the start is creating a remote dev environment and goes into the many ways you can facilitate that via Rust/Fly from the naive to the intricate minimizing syscalls using newer tech and async APIs.