Skip to content

Conversation

@MPParsley
Copy link
Contributor

@MPParsley MPParsley commented Feb 28, 2023

feature-node-16-support is used by https://github.com/redpencilio/ldes-consumer-service/blob/master/Dockerfile#L1

Would it be possible to update feature-node-16-support?

nvdk and others added 4 commits August 8, 2022 15:27
I was kind of surprised we didn't have this in here already. 
the [docker reference](https://docs.docker.com/engine/reference/builder/#expose) specifies this is mostly for documentation towards users of a microservice. I think it's valuable to make it clear that microservices based on the template listen on port 80. Exposed ports are  also used by other "proxy type" microservices such as the letsencrypt companion to figure out how to forward calls to the container in question.

From the reference:
> The EXPOSE instruction informs Docker that the container listens on the specified network ports at runtime. You can specify whether the port listens on TCP or UDP, and the default is TCP if the protocol is not specified.

> The EXPOSE instruction does not actually publish the port. It functions as a type of documentation between the person who builds the image and the person who runs the container, about which ports are intended to be published. To actually publish the port when running the container, use the -p flag on docker run to publish and map one or more ports, or the -P flag to publish all exposed ports and map them to high-order ports.
* Allow overriding port and hostname

* Update server.js

* Update Dockerfile
* Allow overriding port and hostname

* Update server.js

* Update Dockerfile

* Update Dockerfile

* Update README.md
@MPParsley MPParsley mentioned this pull request Feb 28, 2023
@elpoelma elpoelma merged commit 10c2772 into feature/node-16-support Feb 28, 2023
@MPParsley
Copy link
Contributor Author

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants