Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
31–40 of 61 posts
Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#32This looks incredible! Has some serious offerings against the current Self-Hosted PaaS scene, hope I can check it out over the weekend. I have used Dokku[0] in production, and played with CapRover[1] on hobby projects. Flynn was like a better Dokku, before development died.[2] CapRover is a great experience, and it's not a toy IMO. It nails the role of "I want to press a button and have a self-hosted Heroku, with a n…
Is there any reason why you wouldn't use Caprover in production? (other than you haven't needed to)
Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#33This seems very similar in concept to https://caprover.com/
Looks like the main difference is docker compose compatibility but admittedly I have more reading to do. Still tho that is a good difference! I have multiple caprover nodes in prod for hobby stuff so absolutely not knocking it.
Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#34Despite the nice packaging, it appears to be a single-person maintained project. There are quite a few reasons why no opinionated PaaS built on Docker Swarm or Kubernetes (maybe surprisingly) came even close to being a popular choice in the market. Usually, anyone serious who's going to bet on a PaaS that runs their stack will also need a serious corporate entity (i.e. software vendor) supporting the tools in case th…
Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#35Been using Dokku for a year now, and it is quite a joy.
Admittedly, I'm not in the 1000s of requests per second space that many other people operate in (I'm in the internet equivalent of the Mom & Pop website hoster space). I've found Dokku does everything Heroku does, but I get to control it all, which is really nice.
Never tried Caprover or the other container solutions, because I'm not big enough to even exceed single-instance sizes at Hetzner.
My main worries nowadays are:
- What if popularity shot up? How far does my solution scale?
- Hackerzzz. Who is out there just trying to damage something. Not sure it's as bad as the media will have you believe it is, but I still want some relatively strong opsec.
- Disaster recovery. I want to control as much of my stack as possible, so I can fix things when they go wrong, but I just can't seem to shake that eternal worry of 'what have I missed?' in the production DB
I find it quite hard to strike a balance between over engineering things (boy do I wish I had a load balancer that automatically detected an issue with a node somewhere and then did some sort of seamless failover without losing whatever transaction was in progress at the time lol) and just trusting that the thing will work when it has to.
The promise of platforms like Heroku is undeniably less hassle, or a worry-free life, but I don't know whether black-box models can ever truly provide that.
Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#36Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#37Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#38Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#39Is this the first self-hosted PaaS solution also running on Kubernetes? As far as I know neither Dokku nor CapRover do, which always deterred me from these applicationsas I'm running K3s at home.
Re: Apollo – An Extensible Docker-Based Platform as a Service (PaaS)
#40Is this the first self-hosted PaaS solution also running on Kubernetes? As far as I know neither Dokku nor CapRover do, which always deterred me from these applicationsas I'm running K3s at home.