-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
Use a different port than 8080 #170
Comments
I will second this request. Having a way to configure the port to something other than 8080 is a must. |
I'm going to have to disable Docketeer until this is possible, so another +1 here. |
It looks like we can just modify a few files and it should work. I am going to create a fork with a different port than 8080. Which port do you guys think would be best? 5893 seems like a good used port. If I understand correctly, this port is just used internally within docketeer? |
Yea, I think pick something unusual. Would be nice to be able to set an env var (or something) to be able to set it to something if that is also used. I think the problem is that not that it is used internally, but that it listens on that port externally. |
I went with 5893 for now. I agree with making it modifiable within the compose file being the best solution via a variable. It seems to work but unfortunately due to another sign up bug I can not login and test. I even tried making the change with version XII (which is what my code is currently based off of). Edit: I also made some changes to have a .env file with the port configurable. It also seems to work, but unable to fully test without being able to log in. |
Is your feature request related to a problem? Please describe.
8080 is already used by many things...
Describe the solution you'd like
It would be nice to provide a mechanism to specify what port to use, and maybe default to one less common
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: