-
Notifications
You must be signed in to change notification settings - Fork 434
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
Allow specifying a custom port in appsettings.json #79
Comments
I don't know of any http server that does this, mainly for the reason that you have to know the port it's running on to interact with it. If you know that this will always be on 7071, then you don't need to worry about it. If the CLI changes the default port without explicit action, then you'd need to check which port it picked everytime. There is already a |
removing milestone to triage again. |
@ahmelsayed Good point, but we do print out the port once we've chosen it. I guess I was thinking of web project setup in VS where it picks a port (I think randomly). Maybe a better option is to allow customers to specify a port in appsettings.json. |
If the port is specified in appsettings but also command line, command line takes precedence. Should update the help text in port command line option to make it clear. Use a setting at the top level, peer to "IsEncrypted"
|
(edited with new design)
If the port is specified in appsettings but also command line, command line takes precedence. Should update the help text in port command line option to make it clear.
Add a new object "Host" where we can put multiple settings:
The text was updated successfully, but these errors were encountered: