You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been working with Script Kit and encountered concerns regarding my local environment. Specifically, since I'm using Linux within Windows through WSL2 (Windows Subsystem for Linux), I was worried about executing the necessary commands for my workflow.
Upon contacting John, he suggested using the following environment variable to enable command execution in WSL:
# The value should be the full path to wsl, this is what is needed on windows 11.KIT_SHELL=C:\Windows\System32\wsl.exe
After implementing this variable, I was able to run my commands in WSL. This is particularly useful for me as I can now start my docker environment with a single command.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey Folks,
I've been working with Script Kit and encountered concerns regarding my local environment. Specifically, since I'm using Linux within Windows through WSL2 (Windows Subsystem for Linux), I was worried about executing the necessary commands for my workflow.
Upon contacting John, he suggested using the following environment variable to enable command execution in WSL:
After implementing this variable, I was able to run my commands in WSL. This is particularly useful for me as I can now start my docker environment with a single command.
Beta Was this translation helpful? Give feedback.
All reactions