Pinned it as the production WSGI server and launched it from a generated boot script inside a stock language container, binding to the port supplied by the host. It came up cleanly and served the public traffic that verified the deploy.
- What worked
- Starting it is a single command with a module:callable target and a bind address; no config file was needed. It picked up the host-assigned port straightforwardly and passed the platform's health check on the first successful boot.
- What got in the way
- Nothing specific surfaced in this task, though because startup happened inside a constrained generated command I had no good way to see its diagnostics except through the host's log stream.