CapRover: Build your own PaaS
caprover.com
CapRover: Build your own PaaS
1–10 of 183 posts
Re: CapRover: Build your own PaaS
#2Curious as to how this compares to Dokku (http://dokku.viewdocs.io/dokku/)?
Re: CapRover: Build your own PaaS
#3CapRover was mentioned in the thread about the coinbase stack [1] - I guess that's why it's popping up here now.
As I said in that thread - this looks interesting, but the installation instructions put me off a bit. Open a port on your server, and don't change the default password `captain42` - then run a cli tool from your dev machine.
Re: CapRover: Build your own PaaS
#4(non dev) looking to run my own installation of https://github.com/excalidraw/excalidraw for team. Could I use this app? Straightforward to do? How would I estimate the costs?
Re: CapRover: Build your own PaaS
#5For those who have even simpler needs (like side projects, or 1 dev projects), I found using simply docker and git to be plenty enough.
Basically, you can create a bare git repository on your server (`git init --bare`), and put a `hooks/post-receive` script within it that will clone sources in a temporary directory, build the docker image and rotate containers. That way, you can `git push` to build and deploy, and it's easy to migrate server.
The added bonus is that you now have a central git repos that can act as backup, so you don't need github or gitlab.
The main painpoint, which I find dokku interesting for (and I assume caprover too) is zero-downtime deployment. But well, if this is critical, you probably need something more extensive.
Re: CapRover: Build your own PaaS
#6Shameless plug: If you don't want to use containers or are using resource-constrained Linux boxes, have a go at https://github.com/piku :)
Re: CapRover: Build your own PaaS
#7Slightly 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.
Re: CapRover: Build your own PaaS
#8I 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 github, haven't checked out yet if i wanna migrate back) and register your microk8s cluster as a buildrunner.
Thats it you are set. Quite future proof setup, modern, stable, easy to use.
Re: CapRover: Build your own PaaS
#9Another great alternative in this space is dokku[0]. Haven't tried CapRover recently but it looks fantastic.
Re: CapRover: Build your own PaaS
#10Does Caprover support multiple "ingresses"? In that I can have an external load balancer balancing between my clusters servers?
I can't seem to find any info on that in their docs.