Skip to content

instructions on handling delta's in a JS service #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 26, 2023

Conversation

nvdk
Copy link
Member

@nvdk nvdk commented Jan 20, 2023

No description provided.

@erikap
Copy link
Member

erikap commented Jan 26, 2023

Ty @nvdk 🙏

@erikap erikap merged commit a33386a into mu-semtech:master Jan 26, 2023
elpoelma pushed a commit that referenced this pull request Feb 28, 2023
* add expose statement (#39)

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 (#47)

* Allow overriding port and hostname

* Update server.js

* Update Dockerfile

* instructions on handling delta's in a JS service (#48)

* Add documentation to allow overriding port and hostname (#49)

* Allow overriding port and hostname

* Update server.js

* Update Dockerfile

* Update Dockerfile

* Update README.md

---------

Co-authored-by: Niels V <nvdk@users.noreply.github.com>
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.

2 participants