![]() ![]() Sometimes you will need to SSH into one location before tunneling into another. This should get you set up right in the correct directory after you’ve connected. If the workspace was recently used, you can use File > Open Recent > $de-workspace otherwise go to File > Open Workspace. Now open your workspace again with a new connection. code-workspace file somewhere it won’t be picked up by Git There is, however, a workaround to make this a bit less tedious: Wouldn’t it be nice to have VS Code automatically open to the correct folder once your SSH connection is established? Unfortunately there isn’t a way to set a folder location in the settings yet you’d need to click Open Folder and navigate to the project root every time you connect. You may wish to also add the client public keys if you would like. ![]() You’re now connected and can use VS Code’s features like Terminal and Debug Console just like you would locally. Ensure the Windows Hosts public key has been added to GitHub - instructions for adding keys. If your key is on the server, it will state it has your fingerprint and prompt you to continue. If your public SSH key isn’t on the remote server, you will be prompted to enter a password. Click the green Open a Remote Window icon on the bottom left corner, select Connect to Host., and pick your desired host, in this case MySite. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |