[deleted]
CapRover: Build your own PaaS
21–30 of 183 posts
Re: CapRover: Build your own PaaS
#22Slightly nitpicky, but is something a PaaS if you run it yourself? Anything as a Service isn't a service if you're running it yourself. It's just ... infrastructure.
I just read it as short for "cloud infra project with controls modeled after popular PaaS products"
Re: CapRover: Build your own PaaS
#23Slightly nitpicky, but is something a PaaS if you run it yourself? Anything as a Service isn't a service if you're running it yourself. It's just ... infrastructure.
Yeah, it's more like a PaaS alternative
Re: CapRover: Build your own PaaS
#24Curious as to how this compares to Dokku ( http://dokku.viewdocs.io/dokku/ )?
Dokku is best if you only need a single repo support, caprover if you will have multiple apps, and or multiple servers.
Re: CapRover: Build your own PaaS
#25Another great alternative in this space is dokku[0]. Haven't tried CapRover recently but it looks fantastic. [0]: https://github.com/dokku/dokku
I've been using Dokku for a side-project, and it's a really nice tool! My only gripe with it is that it's not easy to deploy an existing docker image. You have to pull it, then transmit it over ssh with "docker save" and "docker load".[1]
Migrating the docker image building from the dokku server to a CI would be easier to do without this. On top of that, deploying an existing software into your machine would be easier.
[1] http://dokku.viewdocs.io/dokku/deployment/methods/images/#de...
Re: CapRover: Build your own PaaS
#26Slightly nitpicky, but is something a PaaS if you run it yourself? Anything as a Service isn't a service if you're running it yourself. It's just ... infrastructure.
Not nitpicky at all - this is an important distinction to highlight for pointy-haired decision makers.
This product is undoubtedly the P in PaaS, but there is no service behind it. If your company uses this as an alternative to a real Heroku/AWS/xyz PaaS, you must have engineers at hand for 24/7 ops, scaling servers and fixing bugs. In my opinion, this is quite risky for anything running in production and should not survive a cost-benefit analysis.
Re: CapRover: Build your own PaaS
#27Background info: https://www.freecodecamp.org/news/how-i-cut-my-heroku-cost-b...
Re: CapRover: Build your own PaaS
#28Looks solid. I am all set for the wave of fully controlled PaaS solutions coming our way. Most of the innovation has stayed locked behind closed rooms at AWS, Microsoft or one of the major cloud companies. This brings in more control and an extra dimension to optimize.
Re: CapRover: Build your own PaaS
#29Curious as to how this compares to Dokku ( http://dokku.viewdocs.io/dokku/ )?
Dokku is best if you only need a single repo support, caprover if you will have multiple apps, and or multiple servers.
How so? I use dokku on A DigitalOcean server for a dozen apps. AFAIK cluster support is different (it exists). What else?
Re: CapRover: Build your own PaaS
#30This tool looks really cool. The section where it listed reasons for using it really struck a chord with me. I am not the most comfortable using all the Linux tools when it comes to setting up servers / system administration. This product looks to be a really good bridge between devs who dev primarily, and those with skills in deployment. Super cool. Thanks for sharing, I will be using this!
Isn't that a setup waiting for disaster to happen? Everything is happily running up to a serious production problem, at which point you miss the experience to debug and fix it.