Earlier quoted context omitted.
I'm a very happy Dokku user, I've been using it for years with no problems, though CapRover seems very interesting.
Given your Dokku experience, do you mostly interact with Buildpacks or Containers? And why?
CapRover: Build your own PaaS
161–170 of 183 posts
Re: CapRover: Build your own PaaS
#162Earlier quoted context omitted.
Hi sneak, I left a comment explaining my journey with CapRover in this HN thread. In there I explained one thing which concerned me was "netdata image in use is spyware #553" which you raised last year. 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…
The version of NetData included in CapRover is a version from before when NetData became spyware, so it’s fine. (Note that I haven’t audited it, that’s just what I’ve been told.) NetData is also optional; I use CapRover and do not opt to install it. Brute forcing a 30 char (or even 20 char) password over the network is infeasible. Do the math. Regardless, as the CapRover developer pointed out in a sibling comment, it…
Re: CapRover: Build your own PaaS
#163Re: CapRover: Build your own PaaS
#164Re: CapRover: Build your own PaaS
#165Earlier quoted context omitted.
I'm a very happy Dokku user, I've been using it for years with no problems, though CapRover seems very interesting.
Given your Dokku experience, do you mostly interact with Buildpacks or Containers? And why?
Re: CapRover: Build your own PaaS
#166Earlier quoted context omitted.
Have you used Dokku before, or did you look at it before settling on CapRover? (I'm just starting to look at both)
I have experience with Dokku, Flynn (also look at this if you're looking at Dokku), CapRover, k8s, and a tiny bit of Nomad. 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. https://flynn.io/ If you're intent on using Dokku, there's a useful web console: https://github.com/palfrey/wharf
Re: CapRover: Build your own PaaS
#167Earlier quoted context omitted.
Given your Dokku experience, do you mostly interact with Buildpacks or Containers? And why?
How do you mean? I never touch the actual containers, I always just let Dokku take care of those, I just push the code with the Buildpack and Dokku handles the rest.
Re: CapRover: Build your own PaaS
#168Earlier quoted context omitted.
The version of NetData included in CapRover is a version from before when NetData became spyware, so it’s fine. (Note that I haven’t audited it, that’s just what I’ve been told.) NetData is also optional; I use CapRover and do not opt to install it. Brute forcing a 30 char (or even 20 char) password over the network is infeasible. Do the math. Regardless, as the CapRover developer pointed out in a sibling comment, it…
Could you quickly explain the math behind this please? Genuinely curious
Brute forcing this, you would have to try every combination. Which means for a four-letter long password: 26x26x26x26 = 456 976 possible passwords.
For a 10 letter long password: 26^10 = 141167095653376 possible passwords.
Re: CapRover: Build your own PaaS
#169Earlier quoted context omitted.
I absolutely agree, were it something commercial these things would need to be considered. Are there any tools you recommend looking into, were I to take the next step? I don't plan on depending on CapRover to fill gaps in my knowledge for too long, but for now this product really is a good start for me.
No problem in depending on CapRover, as long as you are at least somewhat familiar with the tools it sets up for you. Combine that with some crude generic UNIX skills (quickly analyze cpu/ram/disk usage, search in logs, transfer files, modify configs etc.) and you're way better prepared. Ironically it's best learned "on the job" (for me at least); just try to deploy your app from scratch. Play around with nginx/apach…
Re: CapRover: Build your own PaaS
#170For 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…