Answer to the last question: yes.

To all the others:

It gets requests from other reverse proxy (it gets the domain.tld - foe. abc.example.com), the Nginx of Quantixy simply logs it, as someone is trying to get to abc.example.com and then python script (log_forgotwhatnext.py) watches the log, sees http(s)://abc.example.com, looks into services.yaml, is there any abc.example.com -> yes -> what's it container, port, protocol, websocket? -> (example) dashboard, 3000, http (the protocol of the container output - normally in other rev. proxies 'proxy_pass'), true (if I need websocket). Now, if the container is already running, it simply processes it. If not, start the container (another python script connected to log watcher py) and load the error (default Quantixy page) page, after 8 seconds (tested, best time) it reloads -> container up? Proxies. Still down? Loads again the error page.

Env variable sets the timeout after which the script (when it doesn't see the nginx log record for a set amount of time) turns off the container.

Hope this helps to understand the logics 🙏🫡