You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I traced the current container setup: nginx listens on 8080 for both IPv4 and IPv6, and Compose hardcodes 127.0.0.1:8080:8080. A normal host-port conflict can already be handled by publishing a different host port without rebuilding, but changing the internal listener would help host-network deployments and environments that require a specific port.
I can add a runtime OPENCONCHO_PORT setting defaulting to 8080, validate it before rendering the nginx config, and cover the default, custom-port, and invalid-value cases with container tests. I would also document host-port mapping separately. This overlaps the config staging changes in #96, so I would keep the implementation compatible with that read-only-filesystem fix.
Would you welcome a PR with that scope? Is your deployment using host networking, or do you only need to change the published host port? Also, is anyone already working on this?
Activity
utpalsinghdev commentedon Oct 11, 2026
I traced the current container setup: nginx listens on 8080 for both IPv4 and IPv6, and Compose hardcodes 127.0.0.1:8080:8080. A normal host-port conflict can already be handled by publishing a different host port without rebuilding, but changing the internal listener would help host-network deployments and environments that require a specific port.
I can add a runtime OPENCONCHO_PORT setting defaulting to 8080, validate it before rendering the nginx config, and cover the default, custom-port, and invalid-value cases with container tests. I would also document host-port mapping separately. This overlaps the config staging changes in #96, so I would keep the implementation compatible with that read-only-filesystem fix.
Would you welcome a PR with that scope? Is your deployment using host networking, or do you only need to change the published host port? Also, is anyone already working on this?