Is there a quick way to switch traction from default ngrok behaviour to a cloud setting deployment?

[H4LL]

I'm currently using my ngrok agent with a domain to host some services and I'd like to be able to allocate the traction agent a static url on this domain. Ideally I'd run the traction agent serving locally and then i can configure my own port mappings to my existing ngrok/ nginx/ docker configuration, creating tunnels to the relevant ports.

For this I need a compose without the ngrok service. I see that there are environmental variable TRACTION_ENV=local which is used later with ngrok-wait.sh and seems to be a switch to enable or disable ngrok. However, as I set it to something else and remove the ngrok service, I'm beginning to hit subsequent dependencies.

Before I crawl into this rabbit hole, is there an easy way to override the default local ngrok behaviour? Ideally so I can run a local traction service while passing in a static URL for external facing services as opposed to the dynamic ngrok behaviour. TRACTION_ENV makes it seem tantalisingly close.