Env Variable to support external host per protocol

[ankeshgpt153]

Hi @Eugeny ,

I’m deploying Warpgate (v0.23.2-modified) on AWS ECS and had a question about configuring external hosts via environment variables.

Currently, setting:

WARPGATE_EXTERNAL_HOST=tunnel.xxx.com

works as expected, but it applies globally across all protocols (HTTP, SSH, MySQL, Postgres, Kubernetes, etc.).

However, my use case requires protocol-specific domains. For example:

• HTTP / Kubernetes → warpgate.tunnel.xxx.com
• SSH / MySQL / Postgres → tunnel.xxx.com

I tried using environment variables like:

WARPGATE_HTTP_EXTERNAL_HOST=warpgate.tunnel.xxx.com

but it doesn’t seem to have any effect.

So I wanted to clarify:

1. Is there currently any support for setting protocol-specific external_hosts via environment variables?
2. If not, is this something that could be supported (e.g., mapping env vars to external_hosts.http, external_hosts.ssh, etc.)?
3. What would be the recommended approach for dynamic configuration in containerized environments like ECS, where injecting config via env vars is preferred over static config files?

Right now, it seems the only option is to generate a config file at runtime, but I wanted to confirm if there’s a more native or supported approach.

Thanks!