Looks like an open, free, very very early re-implementation of a solution such as Cloudron.io .
Very cool!
CapRover: Build your own PaaS
91–100 of 183 posts
Re: CapRover: Build your own PaaS
#92What does PaaS stand for? The website doesn't say. Platform? Product?
Platform as a service. It's like a step up in abstraction from IAS, infrastructure as a service. The lines begin to blur near the edges though, it's a marketing thing really. Just like "cloud" means many different things to many different people but it's a simple one syllable word perfect for brochures.
Re: CapRover: Build your own PaaS
#93Slightly 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.
”Service” to me is just ”delivery of something with a specific scope and a defined contract”, not so much about who delivers said ”service”.
Many IT depts would do themselves a massive favor to deliver actual services instead of “just infra and some stuff thrown on top” and call it service delivery.
Tools like in this link can help, but a big part is simply about automation and delegation/self provisioning.
Re: CapRover: Build your own PaaS
#94[deleted]
Re: CapRover: Build your own PaaS
#95Re: CapRover: Build your own PaaS
#96What does PaaS stand for? The website doesn't say. Platform? Product?
[deleted]
Re: CapRover: Build your own PaaS
#97What does PaaS stand for? The website doesn't say. Platform? Product?
[deleted]
Re: CapRover: Build your own PaaS
#98Earlier quoted context omitted.
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.
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/apache, letsencrypt, your db stack, packages installation etc. and get a working product.
I'm no expert by far in any of this, but think that knowing "just enough" about these tools really helped along the way. Up to the point where I can now use CapRover like tools with some degree of confidence, closing the full circle ;)
Re: CapRover: Build your own PaaS
#99I 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 ?
Re: CapRover: Build your own PaaS
#100Earlier quoted context omitted.
FYI, you can avoid the $APP directory removal and clone by doing: GIT_WORK_TREE=/home/username/apps/$APP git checkout master
Yes, that's true, thanks for mentioning it. It comes from a time when I did not use docker so I wanted to get rid of build artifacts, but building within docker, this is not a problem anymore.
If you need to use your "old way" for something else, you can use 'git clean -fdx' which will remove all files and directories that git does not track.