We don’t have one yet! It’s part of what we’re doing to release machines.
That last curl should have worked if you’re connected to wireguard, but I’m not positive our HelloNode example listens on IPv6.
To expose it publicly, I believe you need to add and argument like this: fly machine run ... -p 3000:80/tcp:http.
The machines commands are in flux, though, so nothing is guaranteed to work the way I think it does!
We’re launching machines for people who need to build:
- Builders. Our remote docker builders are machines. You could use them to run CI builders, or manage builds for a product like Vercel or Netlify
- Functions as a service: if you want to build Lambda, you can use machines
- Database as a service: if you poke around in branches of GitHub - superfly/flyctl: Command line tools for fly.io services, you’ll see our postgres apps implemented using machines
They’re intended to be driven with API calls. We have a big API mesh that’s not fully rolled out yet, so when you start a machine in Sydney from Sydney, your traffic stays local. It lets you start machines in 500ms or so.
fly machines are a convenience wrapper around the API. When we started documenting the API, we realized APIs are kind of hard to poke at. So the CLI has commands that approximate the API. 