Once could say it requires special knowledge to host a service in the cloud too. The extra step I had to take was to open port 80 and 433 on my server and install nginx to forward the traffic to the right container on my local network since I only have one public IP. It took me minimal research to figure it out.
Sure, you could say that since you put the service on the VPS. But you don’t own the server and host it on your own hardware. Which is what the person you replied to was talking about. Why would you even point out that hosting a service requires special knowledge if you find hosting in a VPS and at home equal?
When you say “hosting in a cloud” vs selfhosting, I think you mean creating an account on a hosted service. Or using something like PikaPods or Fedihost or other managed hosting service. Because once again, hosting in a VPS is selfhosting.
I didn’t say it was “hard”. I said it requires specialized knowledge. Which it does. And which you’ve not disproven in any way.
Once could say it requires special knowledge to host a service in the cloud too. The extra step I had to take was to open port 80 and 433 on my server and install nginx to forward the traffic to the right container on my local network since I only have one public IP. It took me minimal research to figure it out.
You realize hosting on a VPS is still selfhosting? And my comment was about selfhosting?
Sure, you could say that since you put the service on the VPS. But you don’t own the server and host it on your own hardware. Which is what the person you replied to was talking about. Why would you even point out that hosting a service requires special knowledge if you find hosting in a VPS and at home equal?
Not “could”. It is.
When you say “hosting in a cloud” vs selfhosting, I think you mean creating an account on a hosted service. Or using something like PikaPods or Fedihost or other managed hosting service. Because once again, hosting in a VPS is selfhosting.