Steve has the app upstream hardcoded to 127.0.0.1:8083.
That means when e2e: true is enabled, traffic goes:
Caddy -> STEVE :49500 -> app :8083
even if the app’s Procfile says something else like:
ports:3000http_port:3000e2e:trueSo any e2e app that doesn’t listen on 8083 just fails behind steve, usually as some vague upstream/proxy error. This is confusing because the docs/config imply the app can use any unreserved port and http_port should define the HTTP app port.
I think steve should take its app upstream from config/env, e.g. STEVE_APP_UPSTREAM, and the enclave startup should set that from the app’s http_port. 8083 can stay as a fallback for compatibility, but it shouldn’t be the only working app port.
[Steve](https://git.distrust.co/public/steve) has the app upstream hardcoded to `127.0.0.1:8083`.
That means when `e2e: true` is enabled, traffic goes:
```text
Caddy -> STEVE :49500 -> app :8083
```
even if the app’s `Procfile` says something else like:
```yaml
ports: 3000
http_port: 3000
e2e: true
```
So any e2e app that doesn’t listen on `8083` just fails behind steve, usually as some vague upstream/proxy error. This is confusing because the docs/config imply the app can use any unreserved port and `http_port` should define the HTTP app port.
I think steve should take its app upstream from config/env, e.g. `STEVE_APP_UPSTREAM`, and the enclave startup should set that from the app’s `http_port`. `8083` can stay as a fallback for compatibility, but it shouldn’t be the only working app port.