Closed zwolf closed 4 years ago
For the record, it's set in the docker-compose.yml files in the panoptes-designator-[env] in the operations repo. The file in this repo was previously only used for development. Potentially a reason to move that PORT env var out of the k8s tmpl and into the docker-compose file.
It's coming from the config/$env.exs
files https://github.com/zooniverse/designator/blob/1bb80657078df95ea5a9cbbc7a1a80370fe1030a/config/prod.exs#L16
That's where the env var is being loaded, but as I posted above, the env var is defined in in the ops repo docker-compose file.
After merging the last one (https://github.com/zooniverse/designator/pull/93), I started to get yelled at about a missing $PORT env var. This system env var exists on both the prod and staging ec2 instances and is the same on both:
4000
. I can't precisely tell where it's coming from in the current builds but adding it to the template should work.