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.
PaaSS - Platform as a Self Service
CapRover: Build your own PaaS
101–110 of 183 posts
Re: CapRover: Build your own PaaS
#102Curious 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 app…
Dokku supports multi-server deployment via Nomad and Kubernetes as well.
Re: CapRover: Build your own PaaS
#103Earlier quoted context omitted.
> should not survive a cost-benefit analysis I completely disagree, the difference of price between dedicated servers and even EC2 instances is completely amazing. This is what you get for less than $200/month with a dedicated server: 1× AMD EPYC 7281 CPU - 16C/32T - 2.1 GHz, 2 × 1 To NVMe, 96 Go DDR4 ECC, unmetered 750 Mbps In one of my companies the AWS bill is just completely insane, we have like half that hardwar…
Yes, hardware as a service will always be much more expensive than hardware you own. But it may be less expensive than the team you will require to run that hardware at an acceptable service level. It very likely will be less expensive than the opportunity cost of running your own hardware. As an example of the latter bit, if you are running your own hardware and need to add another host and you do not have a spare l…
Or you rent managed servers or colo space from one of the many hosting providers that also offers cloud services, and pick and choose. That lets you migrate your base load to colo or managed servers over time, while you still have the nimbleness of being able to scale up and down dynamically if you want or need to.
And my experience from providing devops services to clients on a contract basis is that the clients who use cloud services tends to need more, not less, devops assistance.
Re: CapRover: Build your own PaaS
#104I'd be interested to know how people who use this kind of thing (or Dokku, etc.) keep their OS, database, applications, etc. up to date, for security reasons if nothing else.
You update your image, stop the container, start the container (with the new image). That's all. You can create complex containers that could update with security fixes without restarting. But it is easier to update an image e.g. once per week/day and auto restart the containers.
Cool, thanks for the info!
I wonder about the underlying instance's OS, though... in the past, for home servers, I've set up cron jobs to get OS updates and reboot, but that seems wrong for a web server I'd like to be always up.
Maybe create a new instance, update the OS, install the app, switchover? Is there automation for this kind of thing?
Re: CapRover: Build your own PaaS
#105I 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…
How does it handle upgrades ?
for me it was seamlessly and I needed to jump a few minor versions.
Re: CapRover: Build your own PaaS
#106Can some developers explain to me why they don't want to set things up themselves? If you already know how to do it, it's not very time consuming. If you don't yet know how to do it, learning how it all works only benefits your understanding of the service you're providing, and empowers you to fix it. It's almost like learning a new trade, and can give you a new perspective how your code runs.
Maybe it's because there's so much arduous research required to finally figure out what magic commands to run to get something to work. Would having a set of HOWTOs that just explain the steps to set up each component work as well for you as a turn-key solution? (It would be great if we could start a trend of people writing a HOWTO.md after writing their README.md)
Re: CapRover: Build your own PaaS
#107Is there anything like this for non web based applications? Looking for hosting for some Python apps pre-procssing data before delivery to clients.
Caprover can run non-web too, from databases to apps
Re: CapRover: Build your own PaaS
#108Does 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.
Should be possible it uses Docker Swarm, which can handle multiple ingress. https://docs.docker.com/engine/swarm/ingress/
You can expose some ports on different nodes and point your external LB (for ex. cloudflare)
Re: CapRover: Build your own PaaS
#109this makes me so happy - to see a PAAS on Docker Swarm! However, I wish the caprover had built this experience on top of kubernetes (or k3s) instead of Swarm. The future of Swarm is really unknown and the ecosystem is undoubtedly behind k8s.
but swarm is much more simpler, I'm concerned about future too.
Re: CapRover: Build your own PaaS
#110Can I deploy apps on different machines with this? E.g. can I run my app on 3 servers with a load balancer?
Yes, that is easy and work right out of the box. You should deploy it with 3 nodes and lat the manager work as the LB (is a single point of failure, though).
A more complex solution would be deploying it with an external LB
EDIT: Rephrased