-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
✨ Utility: Ports #1833
Comments
Or Ports could be a utility in the utilities drawer alongside terminal debug console, and output. |
That makes a LOT more sense... |
@austincondiff, Can this be assigned to me? I have some ideas and started messing around with finding opened ports and even port forwarding. |
@LeonardoLarranaga Thanks for taking this one on! I've updated the issue description with more details and a mockup demonstrating how it might look when complete. Nothing is set in stone so please let me know if you'd like me to change anything or if you have any alternative ideas. |
@austincondiff I noticed you mainly mentioned forwarding ports. Would this mean using UPnP to open ports on the user's router, or instead could CodeEdit open and see ports opened by processes it runs? And then have other solutions like Microsoft Devtunnels available extensions. |
@itjustcrashed I'd imagine we would start with managing and monitoring ports opened by processes that CodeEdit directly controls, focusing on private development workflows. We'd provide optional integration with external tunneling services (e.g., Microsoft Dev Tunnels, ngrok) through extensions, ensuring secure and controlled public access. We might add UPnP support as an advanced feature for users who need it, but we would ensure it is opt-in and clearly communicates the security implications. |
Description:
We should add a Ports utility to the Utility Area in CodeEdit that allows users to manage port forwarding within their development environment. This utility will make it easy for users to forward ports, monitor active ports, and configure various port-related settings from within the editor. The functionality will be visually displayed in a table where users can see port numbers, forwarded addresses, and port visibility (private or public). The user will also be able to interact with individual ports through a context menu.
Expected Behavior
Acceptance Criteria
Screenshots
Note
Please use the
ContentUnavailableView
for the zero-state.Original Issue
I have just built the latest CodeEdit build and used the new feature introduced in #1798, and I noticed that there was no menu to manage open ports. For example, if I ran a web server on http://localhost:3000, an editor like VSCode would show that there is an open port in it's status bar:
What if CodeEdit had open ports in the navigator?
The text was updated successfully, but these errors were encountered: