There is no reason to specify the port in the dockerfile, since the code implementation already falls back to 8080 when no port is provided.
Specifying it in the Dockerfile was causing the --port argument to be ignored, once the Dockerfile uses --force-port by default, which causes it to first check if the PORT variable is present in the environment variables.
This PR should allow people to set their own custom ports using the CLI argument.
smashah
commented
1 year ago
There is no reason to specify the port in the dockerfile, since the code implementation already falls back to 8080 when no port is provided.
Specifying it in the Dockerfile was causing the --port argument to be ignored, once the Dockerfile uses --force-port by default, which causes it to first check if the PORT variable is present in the environment variables.
This PR should allow people to set their own custom ports using the CLI argument.