51–60 of 114 posts
130 apps to get off Heroku is going to a massive pain to get through but it’s looking more and more likely…
This thread will be filled with a ton of alternatives suggesting a "heroku-like experience" on top of some other cloud provider. My honest opinion, don't waste your time with these "shortcuts". Just use the cloud providers directly.
ECS or App Runner on AWS has many of the same issues. 100% agree that many of the k8s-based environment automation solutions are a mismatch for a Heroku replacement. But I do believe there is room for tools that help solve these problems on top of cloud providers (disclosure, working on one at withcoherence.com...)
Earlier quoted context omitted.
Seconded, I'm on DigitalOcean App Platform, with further plans to self-manage it more either on individual droplets or a RKE2 cluster built on droplets, but I keep on kicking the can down the road because I don't need any more complexity
Why do you want so self manage? Saving a few bucks is probably not worth the hassle. I pretty much spend zero time on infra * push to deploy * auto-restart * managed db * easy scaling * s3 object storage * don‘t spend time on updates * web ui (monitoring, basic logging, configuration, ..)
I was pretty unhappy with the outage last night. All the user blogs for https://bearblog.dev went down for about an hour and a half (and I had so many emails to respond to this morning). I'm looking to move Bear over to either a Digital Ocean droplet (I have the staging server running on one with SQlite and Litestream running, and believe it could actually scale well), or to Fly.io (to be seen).
I've got several SQLite + Litestream projects running on Fly, and I've been happy with the service. Here's my config if you'd like a reference: https://github.com/mtlynch/picoshare/blob/b246751d5036fdb332... https://github.com/mtlynch/picoshare/blob/b246751d5036fdb332... https://github.com/mtlynch/picoshare/blob/b246751d5036fdb332...
Lots of astroturfing in this thread. Suggest everyone do their own research before making any moves.
https://news.ycombinator.com/newsguidelines.html
https://hn.algolia.com/?sort=byDate&dateRange=all&type=comme...
I left Heroku in favor of just a hand-configured DigitalOcean droplet. I might try Fly.io but honestly, for what I’m doing, the flexibility of a full Ubuntu box is just too good, even in 2022.
After HOURS of messing around I found this https://devcenter.heroku.com/changelog-items/2446. None of which was communicated to anyone, and it completely breaks all old backups. There's no mitigation listed on the page, and from what I can tell no one can figure out the proper way to do this without manually dumping, manually changing all references, pushing it back up and hoping to god nothing breaks.
I find it absolutely, utterly, unacceptable to do something like this with no migration path documented. Most people (including myself) use Heroku because we're willing to pay more over being a sysadmin. I can run my own infrastructure on bare metal machines, but it's something I deeply, deeply, don't want to do. Much less manually editing 15gb SQL files.
So yes, I'm considering leaving if this isn't mitigated quickly.