Yep. Fly isn't fully baked. Deployed a service earlier this month and got bitten in a few ways: - It took several hours to get a 1 GB disk provisioned (their A

Yep. Fly isn't fully baked. Deployed a service earlier this month and got bitten in a few ways: - It took several hours to get a 1 GB disk provisioned (their API would time out and I'd get left with an allocated but unusable disk that couldn't be deleted without deleting the entire app it was attached to.) The Fly forums have numerous reports of the same issue, going back months, across multiple data centers. All resolved with the moral equivalent of "oops, try again later?" - The fly.toml reference is incomplete and internally inconsistent, documenting keys which are not valid, while omitting valid keys that appear elsewhere in the docs. - Volume snapshots are retained for either 5 or 7 days, depending on which of the multiple conflicting docs pages you believe. - I wanted to let them know about that last one, so I emailed the address listed at https://fly.io/docs/about/support/ https://fly.io/docs/about/support/, only to get an autoresponse saying that they don't read that mailbox and that I should pound sand unless I'm already paying them to read my emails. Reading between the lines of their recent blog posts, it seems like a lot of the infrastructure pains are pinned on Nomad, with the hope that moving to Fly Machines / Apps V2 will obviate a lot of those issues. I hope they're right, because what they're trying to deliver is exactly what I want.