Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Life after Heroku: What's a dev to do?

reaktor.com

Post reply on HN
Print view View original

71–80 of 107 posts

Re: Life after Heroku: What's a dev to do?

#71

Post by t_sawyer »

ysavir wrote: post #36

My biggest take away from trying to find a Heroku alternative is that Heroku is late to the game of charging for a basic app. Other service might be free, but seem to have some sort of catch--only static, or requires a certain infrastructure, or whatever else--and only Heroku had the unopinionated free tier. And while I haven't used their competitors, I'm skeptical they can match Heroku's interface, CLI, add-on ecosy…

It’s not the charging that made me leave.

It was the security breach where all of my environment variables were stolen. And the amount of time it took and their level of transparency through it all.

Re: Life after Heroku: What's a dev to do?

#72

Post by t_sawyer »

I’m personally very happy with switching to a Hetzner dedicated server, I’m saving a ton of money, and the server can handle my busiest months of load with plenty of room to spare.

I use docker containers for a rails app and send backups of my db to S3 with restic. Docker compose files and DR scripts are in my repo. If Hetzner goes down I’ll run them on a VPS from any of the million providers.

Deploys push a docker container to dockerhub, then ssh into Hetzner and pulls them.

If you want the ease of git push deploys similar to Heroku then use Dokku.

Everyone should remember how long it took Heroku to tell you your environment variables were stolen in a breach and how they were not transparent at all through the whole process.

Re: Life after Heroku: What's a dev to do?

#73

Post by matthewcford »

franciscop wrote: post #69
larrymyers wrote: post #35

The article calls out having to learn how to create a Docker image for Fly.io as though it's a bad thing. I consider it a huge bonus if you like taking advantage of free tiers for services. The whole point is that if you're going to take advantage of a free tier you should do so in a way that switching is trivial. Docker goes a long way to achieving that. I personally just pay $10/month to Linode and self host these…

As someone who uses Node.js and is in the exact same situation as the author, requiring Docker is the #1 reason I'm not going with Fly.io. There's a standard for launching a Node.js project, and that's running the "start" script `npm start`, so switching is trivial. I switched from a Linux machine to my current MacBook and I didn't have to make a single change in any of my Node.js projects. Adding docker means adding…

You know you can also use the heroku build packs on fly.io right?

Re: Life after Heroku: What's a dev to do?

#74

Post by LAC-Tech »

larrymyers wrote: post #35

The article calls out having to learn how to create a Docker image for Fly.io as though it's a bad thing. I consider it a huge bonus if you like taking advantage of free tiers for services. The whole point is that if you're going to take advantage of a free tier you should do so in a way that switching is trivial. Docker goes a long way to achieving that. I personally just pay $10/month to Linode and self host these…

Fly.io seems like the easiest way to get a docker container running publically. I had a look at the AWS equivalent (can't remember the name), and it was a cluster fuck of complementary services in the tutorial.

Wish more cloud providers would focus on helping with existing open source tech, rather than trying to suck you in.

Re: Life after Heroku: What's a dev to do?

#76

Post by franciscop »

spoils19 wrote: post #70
franciscop wrote: post #69

Earlier quoted context omitted.

As someone who uses Node.js and is in the exact same situation as the author, requiring Docker is the #1 reason I'm not going with Fly.io. There's a standard for launching a Node.js project, and that's running the "start" script `npm start`, so switching is trivial. I switched from a Linux machine to my current MacBook and I didn't have to make a single change in any of my Node.js projects. Adding docker means adding…

Using Docker is relatively simple and requires little to no configuration, arguably less than a standard node project. Regardless, as someone who uses a variety of languages and is in the exact same situation, my generic Makefile is probably easier to read and understand than any standard that you have probably achieved.

With a standard Node project, you'd need the Node configuration AND the Docker configuration. If I can do without Docker, why not?

> my generic Makefile is probably easier to read and understand than any standard that you have probably achieved

That sounds fairly rude for HN

Re: Life after Heroku: What's a dev to do?

#77

Post by franciscop »

matthewcford wrote: post #73
franciscop wrote: post #69

Earlier quoted context omitted.

As someone who uses Node.js and is in the exact same situation as the author, requiring Docker is the #1 reason I'm not going with Fly.io. There's a standard for launching a Node.js project, and that's running the "start" script `npm start`, so switching is trivial. I switched from a Linux machine to my current MacBook and I didn't have to make a single change in any of my Node.js projects. Adding docker means adding…

You know you can also use the heroku build packs on fly.io right?

I don't use any build packs in Heroku? Since a while back Heroku just recognizes the Node project and automatically works with it, no need for any extra file.

Or do you mean it's the same in Fly.io? If it auto-detects Node.js (through package.json), or at most allows for a dropdown to say "Node.js project", then that sounds about right for me.

Re: Life after Heroku: What's a dev to do?

#78

Post by siquick »

t_sawyer wrote: post #72

I’m personally very happy with switching to a Hetzner dedicated server, I’m saving a ton of money, and the server can handle my busiest months of load with plenty of room to spare. I use docker containers for a rails app and send backups of my db to S3 with restic. Docker compose files and DR scripts are in my repo. If Hetzner goes down I’ll run them on a VPS from any of the million providers. Deploys push a docker c…

Also a Hetzner convert. Their pricing is so cheap for VPS compared to AWS that I worry they’ll have to put up the prices at some point.

Re: Life after Heroku: What's a dev to do?

#80

Post by vlunkr »

franciscop wrote: post #69
larrymyers wrote: post #35

The article calls out having to learn how to create a Docker image for Fly.io as though it's a bad thing. I consider it a huge bonus if you like taking advantage of free tiers for services. The whole point is that if you're going to take advantage of a free tier you should do so in a way that switching is trivial. Docker goes a long way to achieving that. I personally just pay $10/month to Linode and self host these…

As someone who uses Node.js and is in the exact same situation as the author, requiring Docker is the #1 reason I'm not going with Fly.io. There's a standard for launching a Node.js project, and that's running the "start" script `npm start`, so switching is trivial. I switched from a Linux machine to my current MacBook and I didn't have to make a single change in any of my Node.js projects. Adding docker means adding…

FWIW if it’s really that simple to run your projects, then your dockerfile would probably be just a few lines.
Post reply on HN