vscode-remote-oss
vscode-remote-release
vscode-remote-oss | vscode-remote-release | |
---|---|---|
2 | 35 | |
90 | 3,508 | |
- | 1.6% | |
3.0 | 3.0 | |
1 day ago | 9 days ago | |
TypeScript | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vscode-remote-oss
-
The Visual Studio Code Server
There's also remote-oss [1], which is fairly low-level (you have to install it on), but doesn't require you to pass your traffic through the GitHub proxy that Microsoft's service requires (I believe) and is also truly open source (which means, for example, that it can also be used with Codium [2], not just the Microsoft's VS Code distribution).
[1]: https://github.com/xaberus/vscode-remote-oss
- Iām Switching from VS Code to vs Codium
vscode-remote-release
-
Code tunnel to local machine directly (without Azure)
It would be great, if people interested in this feature/having similar problems would consider pushing the following issue: https://github.com/microsoft/vscode-remote-release/issues/8373
-
xdg-open shim for remote ssh to headless server (VSCode)
The other option may require that you add the Remote X11 extension to VSCode (Unless Microsoft has undone the damage they did to their OpenSSH client in the last few years in which case you could just enable X11 forwarding in your ssh options) if you're trying to execute everything from VSCode, and you would have to have a suitable browser or viewer installed on the remote server along with the xdg-utils package (or whatever contains xdg-open if you're not running Debian).
- Remote VSCode over SSH crashes EC2 instance
-
How to execute a file that sets up the environment that is needed for intelisense to work properly?
Take a look at this: https://github.com/microsoft/vscode-remote-release/issues/6375
-
Host pty got disconnected
If it's "The connection to the terminal's pty host process is unresponsive, the terminals may stop working", apparently it's an old problem: https://github.com/microsoft/vscode-remote-release/issues/7964
- Requesting upvotes for vs code dev container postStartCommand issue
-
A step to step guide to set up Dev Container
VSCode with Remote-Container extension installed.
-
SSH on Raspberry Pi using VS Code
Possibly related github issue?
-
Connect from Visual Studio Code to FreeBSD
This might be it.
-
A way to connect to computers via SSH without VPN
Hello! I came across this Github issue that I think would be helpful for remote workers. It's about the possibility to connect to an existing tunnel by using the terminal of OS instead of VSCode UI. This would allow us to use tunnels as a full SSH replacement in scenarios where SSH itself isn't possible. If you think this would be helpful, please upvote the issue here: https://github.com/microsoft/vscode-remote-release/issues/8238
What are some alternatives?
coder - Coder provisions software development environments via Terraform on Linux, macOS, Windows, X86, ARM, and of course, Kubernetes.
pylance-release - Documentation and issues for Pylance
coder-server
rpm-ostree - āš¦ Hybrid image/package system with atomic upgrades and package layering
atom - :atom: Community build of the hackable text editor
patchelf - A small utility to modify the dynamic linker and RPATH of ELF executables
sqlite-jdbc - SQLite JDBC Driver
god-mode - Minor mode for God-like command entering
vscode-web - Visual Studio Code for browser
pyright - Static Type Checker for Python
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
ostree - Operating system and container binary deployment and upgrades