Can I deploy apps on different machines with this? E.g. can I run my app on 3 servers with a load balancer?
CapRover: Build your own PaaS
71–80 of 183 posts
Re: CapRover: Build your own PaaS
#72Can I say it's a poor man's Kubernetes?
K8s does not deal with CI/CD of your source code, nor can it automagically package your code out of the box. You need to compile your source and bundle it in the form of a docker image, host it and provide access to K8s to pull it. K8s is like Linux kernel, it's not usable for most people unless you package it with GNU utilies and other components people expect out of a distro.
Re: CapRover: Build your own PaaS
#73Earlier quoted context omitted.
Not nitpicky at all - this is an important distinction to highlight for pointy-haired decision makers. This product is undoubtedly the P in PaaS, but there is no service behind it. If your company uses this as an alternative to a real Heroku/AWS/xyz PaaS, you must have engineers at hand for 24/7 ops, scaling servers and fixing bugs. In my opinion, this is quite risky for anything running in production and should not…
> 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…
All these things are relative.
When you got applications that don't require high availability while needing a very low cost per CPU, dedicated servers just make sense. We are running a cluster of a few high-CPU dedicated servers for our data-science team, and it just makes sense: we don't need 99.99%+ availability, and the servers we rent are cheaper than the equivalent AWS storage cost alone ... The op cost of managing these is exactly the same as managing equivalent EC2 instances. We don't need backups either.
On the other side, we got some low-CPU web services that require high availability, redundancy and reliable backups. For these I just use Heroku. It's extremely reliable and easy to operate, while only costing about $100/month (a few hobby dynos + a fully managed PgSQL DB). Sure it's probably 5x more expensive than a dedicated server with 10x the performance, but I don't have to worry about backups, availability and scalability. And these apps just don't need this 10x faster CPUs anyway.
Re: CapRover: Build your own PaaS
#74I wonder what happens if something (like mysql) crashes for some reason or something like that happens, would something like that be easier to handle?
Re: CapRover: Build your own PaaS
#75Is there anything like this for non web based applications? Looking for hosting for some Python apps pre-procssing data before delivery to clients.
The web-app integration is completely optional and you can disable it for each app individually.
E.g. your database can be an app that doesn't have any web frontend.
Re: CapRover: Build your own PaaS
#76For 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…
please do!
Re: CapRover: Build your own PaaS
#77Earlier quoted context omitted.
Then I will have to learn then. I feel most productive and comfortable working on a hobby project if I don't need to spend all of my time dotting the i's and crossing the t's with cli and configuration files. I just want to build. I don't see the value investing my time learning the ins and outs of tooling that I will use maybe a few times when it makes minimal impact, as it comes with an opportunity cost for me else…
And that's the problem; by then it's too late (i.e. never took the time to backup the db). It's about finding the balance, writing a PHP app shouldn't involve studying C compilers and CPU design. But I think these tools (whichever you decide to use) are such an essential part of what you're building that "outsourcing" them as much as possible might be a bit ignorant. That being said, as long as it works, it works. An…
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.
Re: CapRover: Build your own PaaS
#78Re: CapRover: Build your own PaaS
#79For 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…
Here is an example of post-receive script I use for that: #!/usr/bin/env bash export APP=appname export DOCKER_OPTS="" unset GIT_DIR rm -rf /home/username/apps/$APP cd /home/username/apps && \ git clone /home/username/git/$APP && \ cd $APP && \ echo building image && \ docker build -t $APP . if [[ "$?" != "0" ]]; then echo "error while building image." exit 1 fi echo "Stopping previous container..." docker stop $APP…
You should at least use `set -u` in this script, otherwise, at some point, you'll fail to set $APP and end up running:
rm -rf /home/username/apps/