They're still decrypting on their nodes, and then re-encrypting before sending to the origin. There's no getting around the fact they can see the traffic as plain text.
You can basically self-host your repos on a cheap VPS. I did that some time ago. You'll have to create a ssh user that has only 'git' as a shell, iirc, on that box. Works okay. But doesn't provide a web ui.
I would not be so quick to judge.
Book are better consumed actively than passively. To me it hints on a desire to absorb what's being read. i.e. a thirst for knowledge that is weighed above material possession.
Using the same software you might use at work and getting better at it, perhaps even exploring simpler distros like K3s, k0s, Minikube or whatever people use nowadays.
It made it trivial for me to deploy reproducible blocks that are also nicely integrated and automated on certain axes (DNS, LetsEncrypt, load balancer / reverse proxy, storage management, PostgreSQL databases with backups).
All of that with considerably easier to understand and debug mechanisms in my experience than doing it with old school configuration management or, even worse, manually.
reply