Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

CapRover: Build your own PaaS

caprover.com

Post reply on HN
Print view View original

61–70 of 183 posts

Re: CapRover: Build your own PaaS

#61

Post by rcarmo »

xu6ahb8E wrote: post #5

For 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…

That is what Piku (https://github.com/piku) is all about. You can easily deploy containers through it as well.

Re: CapRover: Build your own PaaS

#63

Post by dan_can_code »

esquire_900 wrote: post #30
dan_can_code wrote: post #18

This tool looks really cool. The section where it listed reasons for using it really struck a chord with me. I am not the most comfortable using all the Linux tools when it comes to setting up servers / system administration. This product looks to be a really good bridge between devs who dev primarily, and those with skills in deployment. Super cool. Thanks for sharing, I will be using this!

Isn't that a setup waiting for disaster to happen? Everything is happily running up to a serious production problem, at which point you miss the experience to debug and fix it.

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 elsewhere. That's just me though, I have no gripes with people who love to tinker with their set ups. It just isn't my thing.

Re: CapRover: Build your own PaaS

#64

Post by zerubeus »

wiradikusuma wrote: post #59
zerubeus wrote: post #52

Earlier quoted context omitted.

Sort of yes, for personal projects and small business I would go for something like this or dokku and try to split services as much as I can, rather than managing k8s in my own

But if the K8s cluster is managed by cloud (e.g. AWS, Google, even DO), is this/Dokku still worth it (easier)?

Yes dokku still worth it https://news.ycombinator.com/item?id=23460066 and most importantly much easier

Re: CapRover: Build your own PaaS

#67

Post by [deleted] »

Nextgrid wrote: post #39
esquire_900 wrote: post #30

Earlier quoted context omitted.

Isn't that a setup waiting for disaster to happen? Everything is happily running up to a serious production problem, at which point you miss the experience to debug and fix it.

There's also the issue of security. How do you know there's not a big security hole and it's just a matter of time before your data gets stolen or your server becomes part of a botnet or starts serving illegal content? The same thing applies with these turnkey admin panels like cPanel or Plesk and which is why I don't recommend getting anywhere near those.

[deleted]

Re: CapRover: Build your own PaaS

#69

Post by ricardobeat »

zeveb wrote: post #54
1337shadow wrote: post #41

Earlier 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…

That example is not realistic. You rent dedicated servers from a provider that will always have extra hardware at hand, and handle all of those steps; you don't rent hardware yourself and run it in your basement :)

Re: CapRover: Build your own PaaS

#70

Post by esquire_900 »

dan_can_code wrote: post #63
esquire_900 wrote: post #30

Earlier quoted context omitted.

Isn't that a setup waiting for disaster to happen? Everything is happily running up to a serious production problem, at which point you miss the experience to debug and fix it.

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. And if your app is small enough never to get into the grey waters, all the better.

Post reply on HN