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

accept port ranges for ExposePorts config #68

Merged
merged 1 commit into from
Oct 29, 2023

Conversation

marulitua
Copy link
Contributor

As discussed at #66

@NHAS
Copy link
Owner

NHAS commented Oct 16, 2023

Hi there!

Thanks for this merge request and the effort you've put in to make this.

My only comment is that having the port range format using the dash (-) rather than : would be better as its consistent with the other places we define ports in wag.

I understand its written like this because iptables --dport takes that as its port range syntax.

And one small comment is I'm away from computer for a bit so will test and merge when I get back.

@marulitua
Copy link
Contributor Author

Understood will update it

@marulitua
Copy link
Contributor Author

Hi @NHAS please check when you have time

@NHAS
Copy link
Owner

NHAS commented Oct 29, 2023

Yep will do now

@NHAS NHAS merged commit 2b9a5f6 into NHAS:unstable Oct 29, 2023
@NHAS
Copy link
Owner

NHAS commented Oct 29, 2023

Sweet looks good and I've just merged it onto the unstable branch. Thanks for all your work!

@marulitua
Copy link
Contributor Author

Awesome! Many thanks.

@marulitua marulitua deleted the expose_port_range branch October 31, 2023 01:18
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