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
[Feature] Add ability to choose ports through command line arguments #5
Labels
Comments
alextarasov1
added
good first issue
Good for newcomers
hacktoberfest
enhancement
New feature or request
labels
Sep 27, 2019
I'd be willing to give this a go! |
Hello @Silvyre, |
Hi, Alex. Thank you for letting me know! |
Silvyre
added a commit
to Silvyre/RestfulHttpsProxy
that referenced
this issue
Oct 27, 2019
Silvyre
added a commit
to Silvyre/RestfulHttpsProxy
that referenced
this issue
Oct 27, 2019
Silvyre
added a commit
to Silvyre/RestfulHttpsProxy
that referenced
this issue
Oct 27, 2019
Silvyre
added a commit
to Silvyre/RestfulHttpsProxy
that referenced
this issue
Oct 27, 2019
alextarasov1
added a commit
that referenced
this issue
Oct 28, 2019
Resolves #5: adds port selection via command line arguments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Problem
Right now, ports are hardcoded to be
9999
for proxy and9998
for exposed API.This should be configurable because sometimes these ports might already be in use.
Feature Description
Add ability to choose ports through command line arguments. This applies for both the proxy and exposed api. It should be possible to configure both ports independently.
Additional Context
Dockerfile needs to be updated to account for these changes, as well as the makefile.
The text was updated successfully, but these errors were encountered: