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've tried using the Docker image on both Heroku and Google Cloud Run. Both of these services expect to be able to inject the listener port into the container via the $PORT environment variable.
Instead of hardcoding the port to 8080, allow for the listener port to use the $PORT environment variable and then fall back to 8080 if there is no $PORT environment variable defined.
You can set a port for GCR, but since GCR's standard behavior is the same as Heroku's (read $PORT), it would be nice to have the $PORT environment variable available.
The text was updated successfully, but these errors were encountered:
Hey @darinpope, I have just implemented this. Shlink 2.4.0 will support providing the PORT env var while running the docker image in order to change the port in which shlink listens.
Summary
I've tried using the Docker image on both Heroku and Google Cloud Run. Both of these services expect to be able to inject the listener port into the container via the $PORT environment variable.
Instead of hardcoding the port to 8080, allow for the listener port to use the $PORT environment variable and then fall back to 8080 if there is no $PORT environment variable defined.
Supporting docs
Note:
The text was updated successfully, but these errors were encountered: