-
Notifications
You must be signed in to change notification settings - Fork 58
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
Refactor to use single port #56
Comments
will take the opportunity to also move from gorilla/mux to something else since that is now archived. currently, thinking of go-chi/chi since it's close and offers some other niceties such as no dependencies, etc. however, maybe just sticking to standard library is sufficient. |
Hey @wass3r, how is the development? Any timeline on this? Need help with anything? |
@Nepo26 thanks for the interest. not as fast as i hoped :) i had a refactor started that would allow each remote to register endpoints if needed and also set up common ones for metrics/health and then start (one) server with any configured endpoints; i can't commit to a deadline, but i will try to revive that here! |
Currently we expose three ports, for:
Consider refactoring to use a single port. Provide an ability to register a handler for any path and by default register handlers for the above, if applicable.
Also, add a configuration option to set the port the user wants to use.
This will reduce number of ports to expose/manage and allow easier deployments in some cases.
The text was updated successfully, but these errors were encountered: