[Bug] Can't use config file to set port

[rainhead]

Description

Setting Port in config.json has no effect; the server will still start on 8080.

Steps to reproduce

{
    "DevOidcToolkit": {
        "Port": "31389",
        "Clients": [
            ...
        ],
        "Users": [
            ...
        ]
    }
}

$ docker compose up oidc
...
oidc-1               |       Now listening on: http://0.0.0.0:8080

The clients and users do exist, so the config file is being read. Setting the port via environment variable works.

Expected behaviour

server runs on port 31389

Environment details

Docker version 29.2.1, build a5c7197
ghcr.io/businesssimulations/dev-oidc-toolkit:latest                                      60e26c9709b4
Darwin Peters-MacBook-Air.local 25.3.0 Darwin Kernel Version 25.3.0: Wed Jan 28 20:53:31 PST 2026; root:xnu-12377.91.3~2/RELEASE_ARM64_T8103 arm64

[jthomperoo]

I think this is because we're setting the env variables in the Dockerfile, env takes precedence over file config:

ENV DevOidcToolkit__Port=8080
ENV DevOidcToolkit__Address=0.0.0.0

I will have a look at a different way of doing this.

[jthomperoo]

OK, I might just remove the default port being 8080 in the ENV config, though this would be a breaking change for the Dockerfile.

I would then just use the default port of 80.

This would mean this behaviour would work as you would expect with the config file working.

Let me have a bit more of a think on this, since it's a breaking change I want to make sure I get it right.

[rainhead]

I agree that the Dockerfile shouldn't set ENV. Can't you fall back on 8080 in the code if no port has been configured?

Since ports exposed on Docker Desktop all get exposed on localhost, port 80 isn't really workable. I would have preferred something more obscure than 8080, but so far it hasn't been a problem.

[jthomperoo]

Should be resolved in 0.7.0