I run a handful of small PHP apps with Redis and Postgres as add-ons. Max 5 Standard 1X dynos per app.
I want strong GitHub integration and would also like the replacement to be Docker-based.
I imagine there are tons of developers like me out there. And it seems like there are many options. Which ones would you recommend?
Lots of awesome products here, I'd argue that only replit is a true 10x change from the Heroku innovations in terms of providing a next-gen developer experience.
I'm the cofounder of a new company called Coherence, that we think creates a new direction and offers a better platform for the next leap forward. By integrating from dev to prod and capturing the whole SDLC, as well as by operating in your own cloud, we're focused on delivering the best developer experience possible, without compromising anywhere else. For example, by not building 100% on k8s we’re able to offer Cloud Run on GCP or App Runner on AWS, which are “free-tier” friendly without the fixed costs of the k8s baseline infra that other “in your own cloud” providers have. Check us out at https://www.withcoherence.com. We're in an early closed beta so not yet a fit for all teams, but feedback is welcome!
I just use plain Debian, copy my stuff over via rsync and everything works fine.
The machine gets something like 10k users on a normal day. In the past, it occasionally handled 30x that.
I think you can run PHP on there now too; see https://glitch.com/edit/#!/php-poc
For even simpler (static JS/HTML), I just publish on GitLab or GitHub pages.
I utilize it to host many different PHP and Java apps.
Running your own services is not hard, no matter what naysayers tell you. Just give it a try, start small as described a RasPi uses a few watts so you won't even need that solar system here.
I’ve worked as an SRE and do a fair amount of infrastructure work at my job, so I’ve had periods of time where I ran my own k8s cluster for side projects and more recently ran a nomad cluster. The big caveat here is I enjoyed doing this and it helped my career experimenting with infra in my free time before suggesting it internally. I’ve also had bare metal servers and some of the whole classic fabulous monolith thing which is its own beast.
All that said, if you just want some small easy to use compute with little maintenance definitely give Fly a try! (Not affiliated, just a happy new customer)
If you hadn't wanted the Docker-based backing I would suggest trying one of the services that automates setting up your VMs at AWS, DigitalOcean, Linode etc like https://forge.laravel.com/, https://runcloud.io/, https://serverpilot.io/, https://www.cloudways.com/ etc
For me it's the sweet spot between Heroku and AWS.
Any recommendations for two small Node.js applications?
Feel free to ping me: jay@tasker.sh, happy to personally help onboard and toss in some credits if you’d be willing to chat with us about what you’re building!
If as you’re stating, the recent security issues are the main reason, I am pretty sure you’re not going to find a better solution by switching. Any vendor or internal ops team is going to have vulnerabilities. Thinking security issues are limited to Heroku is not logical.
However you might object to the way they handled the security issues. I totally agree with that being a good reason, not because of this specific incident, but because in my opinion, this is a sign of bigger issues at heroku. In short Heroku has been stale from a product point of view and has lost a lot of good talent to deal with product and operational needs they have.
To me, replacing one PaaS with another is not a good idea. All PaaS providers suffer from the same fundamental issues of rigidity (you work around their limitations and not the other way around), price (they can’t transfer commoditisation of the cloud to their customers), and vendor risk (single vendor that can be bought and shut down by the buyer - remember AppFog or Tutum? - or at least lock you in)
Doing it yourself is also not a very wise choice for a lot of people: you either need a devops and SRE team or you’re left copy pasting scripts from across the internet to build and configure your servers.
Alternatively you’re pressed to learn a new tech (kubernetes, dokku, et al) and spend your time on that instead of your app.
I’m a proponent of a middle ground: vendors that take care of devops for you, the way your team would have done so, without the inhibitive costs. Consultancies are one option but they can build something for you at a cost and then you’re left with either keeping them around to maintain it to stuck with a tech stack you can’t manipulate yourself.
Companies like Cloud 66 or any other ones that build and maintain a PaaS like experience on your own servers without their own complex magic are the best ones out there in my opinion.
I’m biased towards Cloud 66 as a founder, but we built it not to build another PaaS, but to try to address the actual question of why everyone starts with heroku and no one seems to stay on it for long.
Simple and easy and we use it for a LOT of things. It does not tie you into dokku itself and you can manipulate everything yourself with docker and nginx.
Dokku is merely an easy interface on top of the OS.
It’s really not hard. Read the docs and you will be up and running pretty quickly.
Then it’s just a simple “gut push dokku master” to deploy your apps.
If you wanna see pure magic, CMD+K —> PostgreSQL (or Redis). ~3s and you’re good to go.