-
-
Notifications
You must be signed in to change notification settings - Fork 237
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
Support for remote workspaces #318
Comments
Hi @Gama11 , First of all, thank you for you PR. I'm on vacation right now, and didn't have the time/resources to properly evaluate it. I'm still not sure how the extension would work with Remotes At first, I thought about working locally which means ignoring remote folders/workspaces, and displaying just the local folders. Then, I thought about supporting remote folders, but as you described, I don't know if there are APIs available for that. If I remember correctly, updating the I'm slowly returning to my OSS projects. Still planning what to do in the next releases 😄 . Stay tuned. |
I'm not sure supporting remote workspaces is the same or even related to the extension running remotely.
Indeed. |
Same here 😄. I see two different scenarios, and not necessarily the extension needs to support both:
In both scenarios, you may have some limitations (like when you use Live Share). In this case, the first scenario (can be used) is almost complete with your PR, because: It is working
It is not working
To fully supports remotes, I think it should have:
But I'm not sure I would make full support (probably not) I don't use remotes that much, and played a little with Containers while bringing the Bookmarks extension to remote (still in alfa stage). |
That's exactly the part that's not 100% working / what this issue is about. In VSCode's "Open Recent" list, you have folders on the local file system in the same list as those Personally I'm not really interested in auto-detection of projects on the remote, that seems unrelated to this. |
I'm playing with it, and I guess I found a way to securely allow the extension to run while connected to remotes. I won't fully support remotes for now, but at least the extension will be available when connected on remotes. What I mean about secure? I would like to avoid issues while using the Stay tuned |
Hi @Gama11 , The other Remote Development issue (#284) has raised a few issues, related to some users which (apparently) were using the extension installed remotely. Once the I've created #323 to gather more information about these scenarios, better understand their needs, and release an update which could be used by everyone. I hope the newly released version works as expected for you. If not, please let me know. |
When working with remote workspaces, Project Manager's "List Projects to Open" command is no longer a good replacement for the built-in "Open Recent...": As far as I know there's no way to let Project Manager know about remote workspaces, while they do appear in "Open Recent...".
Here's an example with a workspace opened via the Remote SSH extension:
It is possible to run the "Save Project" command in that workspace, but this doesn't actually work when you try to open it (the saved project has the path on the remote machine as a
rootPath
).I'm not sure how Project Manager could programatically open a remote workspace. Maybe it would have to invoke a command of the specific remote extension that is used (SSH, WSL, Container...). I wonder how VSCode does this internally in the "Open Recent..." UI.
The text was updated successfully, but these errors were encountered: