Skip to content
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

Built-in port forwarding functionality #6920

Open
1 task done
hos opened this issue Jan 28, 2024 · 3 comments · May be fixed by #24474
Open
1 task done

Built-in port forwarding functionality #6920

hos opened this issue Jan 28, 2024 · 3 comments · May be fixed by #24474
Labels
collaboration The umbrella label for all collaboration features enhancement [core label] setting Feedback for preferences, configuration, etc workspace Feedback for workspace management, layout, interactions, etc

Comments

@hos
Copy link

hos commented Jan 28, 2024

Check for existing issues

  • Completed

Describe the feature

One of the very useful features of vscode is the built-in port forwarding, which persists URLs. This functionality is available in lots of ways outside of the editor (ngrok, cloudflare tunnel...), why I think it will be great to have it in the editor? Well, the most impressive feature of zed was the channels. Though I could use other apps for audio and video calls, and take the notes somewhere else, the built-in one click away calls in the editor means a lot for my current project. I think the port forwarding built into channels may be very useful. For example when connected to the channel the URL https://USERNAME-CHANNEL_ID-PORT will forward to the user's local port.
Checking zed, was a "3 wow per minute" call, when we were trying it with my coworker, mainly because of the collaboration features and I think port forwarding may move collaboration experience farther.

If applicable, add mockups / screenshots to help present your vision of the feature

No response

@hos hos added admin read enhancement [core label] labels Jan 28, 2024
@JosephTLyons JosephTLyons added setting Feedback for preferences, configuration, etc workspace Feedback for workspace management, layout, interactions, etc collaboration The umbrella label for all collaboration features and removed triage labels Feb 1, 2024
@Kashuab
Copy link

Kashuab commented Nov 25, 2024

Would be incredibly helpful for remote dev environments. It'd be nice if I could have a server running on localhost:3000 on the remote server and be able to access it from my client machine at localhost:3000 as well.

@JungeWerther
Copy link

Agree.

For those who are unfamiliar with port-fowarding, it's as easy as running ssh user@hostname -L PORT1:localhost:PORT2 -L PORT2:localhost:PORT2 etc.

I like to create a file connect.sh with e.g.

#!/bin/bash
ssh user@hostname -L 3000:localhost:3000

with chmod +700 connect.sh, run the file ./connect.sh and that's all.

@ConradIrwin
Copy link
Member

This would be amazing!

For SSH remoting particularly, i't's a pain to do SSH; and for collaboration there's no easy solution right now.

@Tebro Tebro linked a pull request Feb 7, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
collaboration The umbrella label for all collaboration features enhancement [core label] setting Feedback for preferences, configuration, etc workspace Feedback for workspace management, layout, interactions, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants