Skip to content
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

Missing the capability to only expose a port #199

Closed
Miaxos opened this issue Oct 13, 2019 · 0 comments
Closed

Missing the capability to only expose a port #199

Miaxos opened this issue Oct 13, 2019 · 0 comments

Comments

@Miaxos
Copy link
Contributor

Miaxos commented Oct 13, 2019

Context:

I got an automated nginx_proxy (https://github.com/jwilder/nginx-proxy) that'll detect automatically if a container is added to his network and for that, you only need to expose ports of the container with a docker run --expose 5000 something and if multiples, specify it with env variables

But with shiplift, it seems we can't only expose a port, we have to map it.

And as the function inside shiplift is called 'expose' to publish ports, I propose to do a function called 'publish' to expose a port (Avoid breaking changes?)

Links:

Well linked to #161 but for only exposing ports.

I did a proposal to add this feature because I used it in a personal project. #198

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

No branches or pull requests

1 participant