Live data from Hacker News

Fly.io: The reclaimer of Heroku's magic

christine.website

11–20 of 320 posts

Re: Fly.io: The reclaimer of Heroku's magic

#11

I don’t feel that way at all. Every time I’ve tried Fly (trust me I’ve wanted to love it), there’s always a rough edge or the service breaks for me. First time I tried it, the web panel wasn’t even loading. Second time, months later, everything was 500ing and I couldn’t find a way to SFTP into a disk (!!!). Total dealbreaker. This was easily done in Render.com with an even more magical experience. Deploy from a GitHu…

Why do you need to SFTP into a disk?

I was moving a Ghost blog from Render. Ghost is notorious for having a difficult time with hosting assets in S3, so it uses disks.

I needed to move the Ghost assets directory for all the posts.

This was a ten minute thing in Render. SOL in Fly.

Re: Fly.io: The reclaimer of Heroku's magic

#13

I don’t feel that way at all. Every time I’ve tried Fly (trust me I’ve wanted to love it), there’s always a rough edge or the service breaks for me. First time I tried it, the web panel wasn’t even loading. Second time, months later, everything was 500ing and I couldn’t find a way to SFTP into a disk (!!!). Total dealbreaker. This was easily done in Render.com with an even more magical experience. Deploy from a GitHu…

Why do you need to SFTP into a disk?

[deleted]

Re: Fly.io: The reclaimer of Heroku's magic

#14
The main thing I want is pipelines - review apps, staging apps, and promotion to production, all integrated closely with GitHub, along with a slack integration that lets me do all of it in a public chatroom.

Until another service has all of this, we’re sticking with Heroku.

Re: Fly.io: The reclaimer of Heroku's magic

#15

I don’t feel that way at all. Every time I’ve tried Fly (trust me I’ve wanted to love it), there’s always a rough edge or the service breaks for me. First time I tried it, the web panel wasn’t even loading. Second time, months later, everything was 500ing and I couldn’t find a way to SFTP into a disk (!!!). Total dealbreaker. This was easily done in Render.com with an even more magical experience. Deploy from a GitHu…

We've been kicking around ideas for managing files on volumes. This is a common problem – it's actually more difficult than you'd expect because "securitah". Once your volume is mounted in one of your VMs, we can't run tools outside the VM to let you manage the file system. On something like k8s with vanilla Docker, we could. But no one should run multitenant Docker.

It's not really an excuse, just a reason it's taking longer to solve than we'd like.

The errors on the web UI sucked. These have improved drastically in the last three months (because we have smart, dedicated people working on fullstack for us now).

Re: Fly.io: The reclaimer of Heroku's magic

#16
post #15

I don’t feel that way at all. Every time I’ve tried Fly (trust me I’ve wanted to love it), there’s always a rough edge or the service breaks for me. First time I tried it, the web panel wasn’t even loading. Second time, months later, everything was 500ing and I couldn’t find a way to SFTP into a disk (!!!). Total dealbreaker. This was easily done in Render.com with an even more magical experience. Deploy from a GitHu…

We've been kicking around ideas for managing files on volumes. This is a common problem – it's actually more difficult than you'd expect because "securitah". Once your volume is mounted in one of your VMs, we can't run tools outside the VM to let you manage the file system. On something like k8s with vanilla Docker, we could. But no one should run multitenant Docker. It's not really an excuse, just a reason it's taki…

Thank you for the response. I want to love your service.

Will keep an eye on the changelogs to see when I can test deploy my apps.

Re: Fly.io: The reclaimer of Heroku's magic

#17

Does fly.io have the same git push deploy magic?

Kind of; flyctl deploy will “magically” build and deploy your app. They show how incredibly easy it is to throw this into GitHub Actions, which I’ve probably done about 8 times in the past week, and it seems to work about as well as you’d expect. (My only deviation from the example is that I limit the branches to deploy to just master.)

To me, flyctl deploy is perhaps even better, because it is VCS agnostic and integrates with existing pipelines. I think it is fully worth it.

Re: Fly.io: The reclaimer of Heroku's magic

#18
post #12

There's a lot of chat about fly.io on HN. possibly just because the founders and friends are posters here. Is there any in depth comparison between them and render.com ?

I think it is because they are refreshingly open about their stack and people love their writing tone.

And the architecture seems solid.

Re: Fly.io: The reclaimer of Heroku's magic

#19
Being a small-scale Heroku user, I have a hard time deciding whether to stay with Heroku or move to render.com or fly.io. Before the latest incident, Heroku seemed to be frozen but stable. Now… I don't know. Are they even trying to bring back Github Connect?

Fly.io seems cutting-edge but I feel I would not profit from their multi-region, close to the user infrastructure. So what are their tradeoffs? Render.com appears more complete (?) and cheaper. But they don't have the same elegant database backups or the pipeline with review apps.

Re: Fly.io: The reclaimer of Heroku's magic

#20
post #12

There's a lot of chat about fly.io on HN. possibly just because the founders and friends are posters here. Is there any in depth comparison between them and render.com ?

Not in-depth, but two things that have stood out to me in assessing Render vs Fly are Render's lack of Multi-region apps and release phase scripts for running migrations. Easy multi-region apps seem to be a main selling point of Fly. However, both of the features I mentioned are on Render's roadmap (Multi-region apps has been on their roadmap since 2019, so maybe not a priority?)
Post reply on HN