And worse: other governments are actively buying into this. German officials were shocked when by Cambridge Analytica, Snowden revelations and even when their phone number on Facebook was leaked. But hey, now that they want to pay for it, they can't be the product, right? Right?🙈
I thought downloading and redistributing tiktok videos was against TikToks TOS?
Which you only agreed to if you have an account (and even then they realistically can only ban your account). If you rehost publically you might get issues with copyright laws though.
Google may have had a moral responsibility to share information if they possessed it, but ultimately, isn't it the government's duty to warn its citizens about such disasters? After all, they are the ones responsible for the safety of the people they govern.
Absolutely, it is not necessary if the proxy can reach the service in other ways (e.g. a shared network). Some non-http services don't like to be proxied though. Some constellations where the proxy is not on the same host as the containers may also make it necessary. My answer was based on the possibility to not have the same inside/outside port, not necessarily the need though😉
Welcome to the community then :) For rootful Docker you are correct - the inside port can be 80 and you can expose it on whatever port you want (ideally you expose it only via reverse proxy and not by port - I can recommend Caddy-Docker-Proxy for that)
Unless I am missing some obvious setting:
Restricted Kubernetes doesnt work like that. You have to run the container with a non-root UID (usually something upwards of a million). Non-root users however can't reserve ports below 1025. Nextcloud builds on the default php-apache image which comes with the default apache ports.conf (Listen 80).
So now this has to be overwritten either by making a custom build (which may require creating a custom build pipeline) or by mounting a new config file (e.g. via ConfigMap) else it wont start. Both are an additional update risk which now has to be documented and checked before updating in addition to changes from the normal nextcloud changelog.
Similiar issues probably appear with rootless docker/podman unless you add extra capabilities, which is not possible in restricted kubernetes settings.
As long as it is configurable, ideally via env, I dont care about the port.
This could be important for restricted Kubernetes clusters (or certain Gluetun configs). Don't be Nextcloud with their default port of 80 in their Apache image with only hacky ways to change that. God, I hate Nextcloud. They are truly becoming the next Wordpress.
The perfect business case: AI users watching AI ads before AI videos. No pesky users to deal with👍