-
Notifications
You must be signed in to change notification settings - Fork 40
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
default port tcp #99
default port tcp #99
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please have a look at the broken test suite.
I removed myself as a reviewer as I neither use nor maintain this package. I just commented on the broken build to speed up the review process for the core maintainers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should also add some tests 👍
more on port mapping. | ||
``EXPOSE`` d port to be available on ``HOST_PORT``. In the case where | ||
the protocol is not specified, tox-docker assumes tcp, as per the | ||
dockre default. See below for more on port mapping. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo here
I'm leaning towards not accepting this -- the inconvenience of having to type "tcp:" seems a small and infrequent price to pay for greater explicitness in the tox-docker config. Does anyone feel really strongly about this? |
Doing this is aligns tox-docker more closelt with docker. My bias is to
standardize on the behaviour of the tool with which I'm integrating. I
expected tox-docker to require port declarations to match the docker
syntax, it helps reduce the barrier to entry.
…On Mon., May 24, 2021, 21:47 Dan Crosta, ***@***.***> wrote:
I'm leaning towards not accepting this -- the inconvenience of having to
type "tcp:" seems a small and infrequent price to pay for greater
explicitness in the tox-docker config. Does anyone feel really strongly
about this?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#99 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKFVRTQPMRAWLQSCVT6EXTTPKNLXANCNFSM45GSZCWQ>
.
|
@gaborbernat Happy to add the tests and finish this off. But if @dcrosta doesn't want this behaviour then we should kill it off. |
Ping @dcrosta do you have a preference - prior to my writing the tests? |
Given the lack of answer - I assume we don't want this. Closing. |
closes issue #98