Live data from Hacker News

CapRover: Build your own PaaS

caprover.com

111–120 of 183 posts

Re: CapRover: Build your own PaaS

#111
post #7

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.

”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.

You can't just decide that words mean different things to "you".

Platform as a Service or anything "as a Service" means someone else provides it as a service (ie subscription). The Platform part is all this is offering. So it is not a Platform as a Service.

Re: CapRover: Build your own PaaS

#112
post #68

Earlier quoted context omitted.

Is there something wrong with nginx?

I can't trust something that may now be under the control of the Russian state.

But you're fine with Caddy or traefik "that may now be under the control of the United States"?

All 3 of these are open source on github with widely used code bases that are free to view and read as you want.

Re: CapRover: Build your own PaaS

#113

Earlier quoted context omitted.

I can't trust something that may now be under the control of the Russian state.

But you're fine with Caddy or traefik "that may now be under the control of the United States"? All 3 of these are open source on github with widely used code bases that are free to view and read as you want.

The US government hasn't raided the homes of the primary developers of those, though.

I'll admit that the open source nature limits the damage a state actor can do, though.

Re: CapRover: Build your own PaaS

#114

Earlier quoted context omitted.

”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.

You can't just decide that words mean different things to "you". Platform as a Service or anything "as a Service" means someone else provides it as a service (ie subscription). The Platform part is all this is offering. So it is not a Platform as a Service.

Yes, ”someone else” - be it delivered internally from one team to others or b2b.

It is not necessarily hard tied to a business model, but of course I understand that this is the common usage.

It’s really about abstractions and consumability.

This is my interpretation of the NIST meaning of aaS.

Re: CapRover: Build your own PaaS

#115

Earlier quoted context omitted.

But you're fine with Caddy or traefik "that may now be under the control of the United States"? All 3 of these are open source on github with widely used code bases that are free to view and read as you want.

The US government hasn't raided the homes of the primary developers of those, though. I'll admit that the open source nature limits the damage a state actor can do, though.

That you know of ;)

If you are going to go full paranoid, you can't pretend that the media is 100% trueful at every aspect, especially when it comes to internal US affairs.

Re: CapRover: Build your own PaaS

#116

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

> you'll need a HTTP server for each site

isn't that what virtualhosts are for?

Re: CapRover: Build your own PaaS

#117

Earlier quoted context omitted.

The US government hasn't raided the homes of the primary developers of those, though. I'll admit that the open source nature limits the damage a state actor can do, though.

That you know of ;) If you are going to go full paranoid, you can't pretend that the media is 100% trueful at every aspect, especially when it comes to internal US affairs.

Which is why I'm only 1/8th paranoid, not full paranoid. =P

Also, while every media source is biased, if you review enough angles on a given story, you can arrive at some semblance of a true account.

Re: CapRover: Build your own PaaS

#118
post #54

Earlier quoted context omitted.

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 :)

What you just described is a kind of hardware service!

Re: CapRover: Build your own PaaS

#119
post #68

Earlier quoted context omitted.

Is there something wrong with nginx?

I can't trust something that may now be under the control of the Russian state.

Would you mind to elaborate? I haven’t heard anything about Nginx being “compromised” before
Post reply on HN