I have been using CapRover and love it. I donate to their OpenCollective[1]. For those noting "why don't you just use Linux / k8s / ...", that feels close to the original complaints re: Dropbox on Hacker News[2]. I've run clusters hundreds of nodes in size myself but CapRover gives me the pleasure of not having to sweat the small details. You can get this from other platforms but usually there's a dollar cost tied to…
CapRover: Build your own PaaS
141–150 of 183 posts
Re: CapRover: Build your own PaaS
#142I have been using CapRover and love it. I donate to their OpenCollective[1]. For those noting "why don't you just use Linux / k8s / ...", that feels close to the original complaints re: Dropbox on Hacker News[2]. I've run clusters hundreds of nodes in size myself but CapRover gives me the pleasure of not having to sweat the small details. You can get this from other platforms but usually there's a dollar cost tied to…
Have you used Dokku before, or did you look at it before settling on CapRover? (I'm just starting to look at both)
Re: CapRover: Build your own PaaS
#143Earlier quoted context omitted.
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 app…
Dokku supports multi-server deployment via Nomad and Kubernetes as well. - https://github.com/dokku/dokku-scheduler-kubernetes - https://github.com/dokku/dokku-scheduler-nomad
Re: CapRover: Build your own PaaS
#144Re: CapRover: Build your own PaaS
#145For 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…
I actually developed a system similar to this but used docker compose as an alternative to Procfiles and nginx+le to handle dynamic virtual hosting. It's actually a golang app that will automatically provision git repos with the necessary hooks and also allow you to exec into a container directly over SSH. I had the thought of using docker stack to achieve zero downtime but haven't had a chance to try that out. Happy…
Re: CapRover: Build your own PaaS
#146I have been using CapRover and love it. I donate to their OpenCollective[1]. For those noting "why don't you just use Linux / k8s / ...", that feels close to the original complaints re: Dropbox on Hacker News[2]. I've run clusters hundreds of nodes in size myself but CapRover gives me the pleasure of not having to sweat the small details. You can get this from other platforms but usually there's a dollar cost tied to…
Have you used Dokku before, or did you look at it before settling on CapRover? (I'm just starting to look at both)
I think CapRover has the best experience out of the Dokku/Flynn/CapRover "group". Not a huge Dokku fan. Would use Flynn over Dokku again, but I'd rather use CapRover over both.
If you're intent on using Dokku, there's a useful web console:
Re: CapRover: Build your own PaaS
#147how is this any different than setting up grapahana, nginx-proxy with letsencrypt companion etc with docker-compose and just replace my app image?
Re: CapRover: Build your own PaaS
#148Re: CapRover: Build your own PaaS
#149I was hoping to move over, but I won't just yet. Was hoping for two factor auth support [2]. The dashboard was publicly facing and only guarded by a password.
There was also an issue which concerned me: 'netdata image in use is spyware' [3] - however I have not digested that thread and its related discussions to understand if it's a genuine issue yet.
Finally, I was hoping to understand more about the motivations of the project. Who's funding this project? The OpenCollective [4] page shows an annual budget of $529.55 USD? What are the long term goals? How can they sustain themselves?
I use PM2 for running some of my Node.js apps, but I can see there's also PM2 Plus and PM2 Enterprise [5] which helps me understand how they're able to sustain the free version.
I don't mean to be pessimistic towards a piece of software which actually works extremely well. Just want to better understand its long-term suitability for deploying production-grade applications.
[1] https://news.ycombinator.com/item?id=23278095
[2] https://github.com/caprover/caprover/issues/493
[3] https://github.com/caprover/caprover/issues/553
Re: CapRover: Build your own PaaS
#150I have been using CapRover for about half a year now on my personal server running multiple projects. It does what you'd expect and the configuration format is pretty easy to use, using any docker image directly works without any extra steps, just enter the image name and it'll do the rest. I'm pretty happy with it and will probably stay with it for the time being. It's not the best for hosting many static pages, as…
Single factor is more than fine in the case where you know the admin (yourself) is going to use a 30 char random password and use a password manager that won’t autofill it on phishing domains.
I haven't yet gone through the discussion but would you mind letting me know if you're satisfied with the outcome? You appeared to be fighting for increased privacy, so thank you.
Also you'll see that in my comment, I raised another issue RE: lack of two factor auth. I'm curious, why do you think single factor auth is fine? Simply because brute force for a 30 char password is not practical on todays hardware? Or is there something I'm missing?