-
Notifications
You must be signed in to change notification settings - Fork 1.3k
group and give description for gitpod ports #9285
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
Comments
There is another use case for this: In some cases, frameworks, or even integrations with Gitpod open ports for their own use, however, it's not always explicit where this port came from/why it's been opened. Having descriptions and encouraging explicit naming or descriptions of ports could make it more clear when there's an unknown / undefined opened port, possibly by grouping or labeling these ports as unknown. We could also take a look at guessing what the port might be related to by inspecting the parent process. |
@konne It actually supported: But we are missing docs about it, sorry. |
@akosyakov thx & cool. I will asap add it to our config. |
I'm closing it, please reopen if it does not work. For auto derived name and description: #3374 |
@akosyakov do you also plan to implement grouping.
|
@akosyakov names and descriptions are working |
Should it work based on |
@akosyakov can you please add this ticket to the epic, thanks |
the current port list just contains all currently shared ports.
This is very confusing because we open for example a lot of nodejs debugging ports that are not needed to be used by the users.
It would be great to first have a possibility in the gitpod.yml to give a group name
On Top it would be even great to give each port also a description that would be visible beside the port number like
ports:
port: 33000-33999
...
port 330100
port 330101
port 6008
The text was updated successfully, but these errors were encountered: