21–30 of 189 posts
> The main motivation to migrate was cost. Is Fly.io really than much cheaper for hosting CDN/Postgres/Docker Container?
I saved about 25% from Heroku, but fly is much less reliable. I've had TLS certs expire without warning and redis has timeouts
I see closed connections on low traffic redis connections - for now a dumb catch-and-reconnect is doing ok
I recently migrated some services from DigitalOcean to Fly and it was quite pleasant. My only issue is that routing to Fly from Southern California is awful. My friend and I have different ISPs and yet we’re both routed to the east coast instead of the much closer Los Angeles edge server. So our requests end up going to the east coast(edge), then back to the west coast (app), back to the east coast(edge), and then ba…
I missed when this was added: > if you configure your application to expose a Prometheus endpoint, those metrics will automatically show up on your Grafana dashboard But that's such an amazing and simple idea to integrate observability. Love the approach.
Isn't this just how Prometheus works alongside Grafana? I've never used fly.io but I've used that exact setup with these two services.
Nothing special vs vanilla prom/grafana, but seamless “no-ops” integration vs DIY.
I found debugging setup errors on fly to be incredibly frustrating You can't even ssh until the container started and they have some requirements on hostnames (0.0.0.0) At least a few of their examples are broken. The documentation could be better but it's pretty good Is it better than Aws? Yes of course, you need to spend way more to get a dx as bad as Aws. Setting up a VPS is a smoother experience than fly, though.…
Help me understand what you'd be SSH'ing into before your VM boots up? (I'm responsible for most of our SSH goop, so if there's an improvement to be made, I'm happy to make it). A reminder: we don't run "containers". We take containers, unpack them, and transform them into VMs. There's no host OS for you to access.
I recently migrated some services from DigitalOcean to Fly and it was quite pleasant. My only issue is that routing to Fly from Southern California is awful. My friend and I have different ISPs and yet we’re both routed to the east coast instead of the much closer Los Angeles edge server. So our requests end up going to the east coast(edge), then back to the west coast (app), back to the east coast(edge), and then ba…
This is uncommon. When did it happen? We had some cross country routing issues a few weeks ago. We can generally fix these if you don't mind sending us traveroutes.
> The main motivation to migrate was cost. Is Fly.io really than much cheaper for hosting CDN/Postgres/Docker Container?
I saved about 25% from Heroku, but fly is much less reliable. I've had TLS certs expire without warning and redis has timeouts
People who proxy through cloudflare hit this a lot, unfortunately.
Just like Heroku.
Earlier quoted context omitted.
This is uncommon. When did it happen? We had some cross country routing issues a few weeks ago. We can generally fix these if you don't mind sending us traveroutes.
This is cool, I'd love to know more about how you generally fix issues like these?
Routing issues like this are typically the result of some weird network provider politics. The fix is typically ti change how we announce IPs to force a route to do something we want. It's a dark art.
Isn’t Fly.io hosted on AWS (they don’t have their own hardware). Just like Heroku.