You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
tjcran
changed the title
Enhancement: Log out where the webui is being served
Enhancement: print out to terminal where the webui is being served
May 11, 2022
I'm assuming this is for coder server, but it's not clear to me where this should be printed and/if it's different from access-url which we're already printing?
access-url: http://127.0.0.1:3000
Are there situations where access-url is not printed? Or is it not descriptive enough?
I'm assuming this is for coder server, but it's not clear to me where this should be printed and/if it's different from access-url which we're already printing?
access-url: http://127.0.0.1:3000
Are there situations where access-url is not printed? Or is it not descriptive enough?
access-url is not the listening port. Eg it can be a tunnel.
access-url: https://fervent-austin7.try.coder.app
As a developer, I like when the logs state which port is being listened on locally
I think the current experience in the CLI accounts for this, maybe in a slightly different way, and this is now somewhat irrelevant. Feel free to re-open if you disagree.
Currently I don't know where my ui was served, it would be nice to see
listening on localhost:3000
or something in the logs.The text was updated successfully, but these errors were encountered: