At a higher level of operation, companies are switching to immutable infrastructure.

So you don't need to SSH to debug, you'd just re-deploy another container or something.

However, there's an <<extremely>> long tail of places, equivalent to mom and pop stores, where SSH will still be in use for a long, long time. I include antiquated banks or government in "mom and pop stores" for the purposes of this discussion :-p

> So you don't need to SSH to debug, you'd just re-deploy another container or something.

I've still never seen a place where this was true.

At some point you always run into a situation where you need to see what's happening inside the container in production at a level of detail that isn't available except by directly connecting. So you attach a sidecar with SSH, or you deploy a debug version of your container that runs SSH, and then you SSH into your container and see what's happening.

I mean, the example you gave of what you use ssh for is itself an obsolete function. Using a personal Unix server to host a personal website is not really any different than making your own clothes using a sewing machine. It is perfectly fine - but it's a niche activity done by hobbyists who enjoy the process itself.

How should I be hosting my website then? Suppose for the sake of an example it's some simple custom HTML, CSS, and a few javascript math apps. I don't enjoy the process, I just need the damn website online.

(Again – an honest question! I was never formally instructed in these matters.)