-
Notifications
You must be signed in to change notification settings - Fork 222
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
vscode extension? #610
Comments
Related issue on the other side: microsoft/vscode-remote-release#3345 |
There's a PR open here that allows connecting VSCode easily to a Toolbox container via Remote-SSH extension. Another possible approach would be to make toolbox able to export a suitable devcontainer.json file for use with Remote-Containers extension. |
Yes, that's #587 |
Let's close this issue and follow-up in the other respective issues. |
I was able to attach to my Toolbox container through VSCode's Remote-Containers extension. All I have to do is:
{
"remote.containers.copyGitConfig": false,
"remote.containers.gitCredentialHelperConfigLocation": "none"
} |
@debarshiray from my regular tests here, the settings above are enough to allow me to work comfortably within a Toolbox container via VSCode's Remote-Containers extension. You may consider adding a feature to |
containers/toolbox#610 (comment) Signed-off-by: anthr76 <[email protected]>
Is your feature request related to a problem? Please describe.
I love toolbox but I don't use it daily because I'd have to type
toolbox enter
every time.I develop mainly from vscode and I'd love it if there were a way for it to work always inside the toolbox. Or at least to do it by default.
VSCode supports remote development, and one of the specifically supported environments are containers.
Describe the solution you'd like
I'd like it a lot if there was a "Remote - toolbox" extension that, once installed, lets you just choose the toolbox name for your environment (if you want; otherwise just use default one). Then that would make VSCode do all of its stuff inside the toolbox and not outside of it.
Describe alternatives you've considered
Using the above linked containers extension to configure it to develop inside toolbox, but I don't think it's possible. If it were, some docs on how to do that would be just enough.
The text was updated successfully, but these errors were encountered: