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

CapRover: Build your own PaaS

caprover.com

Post reply on HN
Print view View original

31–40 of 183 posts

Re: CapRover: Build your own PaaS

#31

Post by MrCheese »

Nextgrid wrote: post #2

Curious as to how this compares to Dokku ( http://dokku.viewdocs.io/dokku/ )?

CapRover has support for multi-server deployments using Docker Swarm. It also has a nice dashboard with built-in monitoring and such. There is a marketplace of sorts with single-click deployment for certain applications.

Dokku on the other hand has support for buildpack deployment as well as Procfile support for running multiple processes.

I prefer Dokku. The main reason is that I only need a single server for my apps and running Docker Swarm adds complexity.

I wrote about some other differences in my blog: https://www.mskog.com/posts/heroku-vs-self-hosted-paas/

Re: CapRover: Build your own PaaS

#33

Post by xu6ahb8E »

Longwelwind wrote: post #25
hardwaresofton wrote: post #9

Another 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 easie…

dokku is also meant to build a custom image on deploy : rather than using heroku's buildpacks, you can put a Dockerfile at the root of your project and it will be used instead.

So basically, you could put a Dockerfile file container just FROM and MAINTAINER, referring the image you want to use in the FROM, and dokku will download and execute it on `git push` (provided it can access to the image repository).

Re: CapRover: Build your own PaaS

#34

Post by MrCheese »

fullito wrote: post #8

I can recommend in getting in k8s with something like microk8s from ubuntu: You will learn k8s and you will get the same thing as they do but with open components, industry standards and a whole industry moving in this direction. I have already microk8s running at home with argocd. I have never had IaC that quick and that simple setup. With traefik you can have your domains as well. Then just go to gitlab (or now to…

How does the deployment process differ from CapRover/Dokku?

Deploying a simple app with a database with Dokku is something like: 1. Run command to create a database of your choice(Postgres, MySQL, Redis etc) 2. Run command to create application 3. Run command to link the database to the application 4. Push to the Dokku repo to deploy the application.

Re: CapRover: Build your own PaaS

#35

Post by JackFr »

esquire_900 wrote: post #30
dan_can_code wrote: post #18

This 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.

Well, I wouldn’t say I miss it ....

Re: CapRover: Build your own PaaS

#36

Post by 1337shadow »

onion2k wrote: post #7

Slightly 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.

Nope, you have IaaS (Infrastructure as a Service) like OpenStack, and PaaS (Platform as a Service) like OpenShift, KelProject, CapRover ...

The idea is that you ask OpenStack a VM and it will give it to you, dealing with the lower level details for you.

PaaS means that you ask it to deploy a service and it will deploy it for you, dealing with lower level details for you.

Re: CapRover: Build your own PaaS

#37

Post by dgb23 »

Nextgrid wrote: post #2

Curious as to how this compares to Dokku ( http://dokku.viewdocs.io/dokku/ )?

Their copy writing is funny and honest, I like it!

When it comes to operations I often feel overwhelmed, even though I've done DevOps and automation work in the past.

Most of the things I'm working on professionally don't need the "scale" part, but the "robustness" and especially "ergonomics" parts. When I look at most infrastructure solutions, then I often get a combination of "this is too complex" and "I don't need this".

So I was drawn to solutions like Heroku at some point, but there you cannot even do the most basic thing: persistently writing to the filesystem. So you are forced to introduce system level complexity and coordination for such a fundamental feature.

Naturally I tend to prefer simple tools that enable things rather than constrain them.

Side note: I think when the "code has to run on some computer" problem is finally solved, then we likely see an explosion in productivity in our industry.

Re: CapRover: Build your own PaaS

#38

Post by ghaff »

1337shadow wrote: post #36
onion2k wrote: post #7

Slightly 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.

Nope, you have IaaS (Infrastructure as a Service) like OpenStack, and PaaS (Platform as a Service) like OpenShift, KelProject, CapRover ... The idea is that you ask OpenStack a VM and it will give it to you, dealing with the lower level details for you. PaaS means that you ask it to deploy a service and it will deploy it for you, dealing with lower level details for you.

Neither you nor the parent are wrong but I'd argue that you don't really see IaaS or PaaS used all that much for on-prem platforms these days. (And the definition of PaaS was always a bit fuzzy--something like an abstraction that is in between IaaS and SaaS.

You're probably more likely to see OpenStack called a private cloud or on-prem cloud than "IaaS" these days. And OpenShift is usually called a Container Platform rather than a PaaS.

Re: CapRover: Build your own PaaS

#39

Post by Nextgrid »

esquire_900 wrote: post #30
dan_can_code wrote: post #18

This 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.

There's also the issue of security. How do you know there's not a big security hole and it's just a matter of time before your data gets stolen or your server becomes part of a botnet or starts serving illegal content?

The same thing applies with these turnkey admin panels like cPanel or Plesk and which is why I don't recommend getting anywhere near those.

Post reply on HN