And this is the equivalent for cgi-bin "vi ~/public_html/cgi-bin/hello.sh"

And the code itself did not contain 10 lines of vendor specific scaffolding to run either but were straigt onto the business logic.

Where is the platform where i can take an completely standardized scriptfile use my preffered ftp/scp client and upload it into an runtime configured to run inside of the corporate firewall?

You are missing having IT set up a UNIX server instance, with Apache or NGINX on it, configure firewall, public IP DNS entry, and then having the rights to ftp/scp into it before being able to call vi into hello.sh.

So if you want that approach then, IT would set an "static HTML web app" instance for "~/public_html" version, which you can then ssh into.

https://docs.microsoft.com/en-us/azure/app-service/configure...

or have a VSCode like experience editing directly your site files,

https://social.technet.microsoft.com/wiki/contents/articles/...

I feel like you must know this, but the convention back in the day was a UNIX server for an organization, that would handle essential tasks like email, that everyone could log in to and have access to common UNIX tools, and that would automatically serve "/home/$USER/public_html" as static HTML web apps under example.com/~$USER.

So, IT sets the server up once and maintains it and provisions and deprovisions accounts, but everything else is self service. There's no need for IT to be involved when somebody wants to "launch a new web page". It was a pretty nice system for what it was.

Sure and I get from where you are coming, but those days are long gone, in fact by 2004 that wasn't a thing at Nokia any longer.

But is the new way better for all usecases?

From security point of view, yes.

yes but if that's the only way it's approved there is a huge unfilled gap in the current market.

Besides given the near constant issues we see around misconfigured s3 bucket i am not sure the average cloud function meets security standard anyway.