Fabric and Visual Studio Code Windows #124
Replies: 7 comments 4 replies
-
The above set me on the right path and, I didn't even know about WSL which is even better because it is quite awesome. |
Beta Was this translation helpful? Give feedback.
-
Very cool! |
Beta Was this translation helpful? Give feedback.
-
Any other way to install it other than using WSL? |
Beta Was this translation helpful? Give feedback.
-
I was able to get Fabric up and running via WSL. I'm curious what other folks use in place of |
Beta Was this translation helpful? Give feedback.
-
Another follow up from me. I was able to get fabric working in a vs code terminal without WSL. I haven't done much testing on it but so far it seems to be working comparably well. I haven't been thru the pull process yet though to update. Hopefully that won't cause issues. I posted what I did to get it working here: #183 (comment) |
Beta Was this translation helpful? Give feedback.
-
I have OLLAMA working on the Windows host and a perfectly running fabric on the WSL Linux Ubuntu host, now how do I get the two of them talking?
|
Beta Was this translation helpful? Give feedback.
-
Following up to my comment above, I read the Ollama issue here: ollama/ollama#703 In PowerShell, I do this:
And now in the WSL Ubuntu environment, I can see this:
And I can now see this, using the default gateway:
But I'm still not seeing the local models in fabric:
Any ideas for how to get local models working in Windows/WSL? |
Beta Was this translation helpful? Give feedback.
-
Just an update of the saga of my trying to do the installation of fabric using Visual Studio Code in Powershell terminal. To make life easier for yourself and be able to follow the Readme.md instructions verbatim you need to install the extension Windows Subsystem for Linux. To do this in Visual Studio Code go to File \ Preferences \ Extensions and look for it there. Now I'm not sure if you first need to turn this on as an App Feature within Windows first before seeing it on the list of Extensions in Visual Studio Code but if you don't see WSL as an optional Extension then proceed to follow the instructions to do that in Windows. At google just type in turning on Windows Subsystem For Linux App Feature in Windows and follow the instructions. Pretty straight forward. Again I'm not sure if you need to do this outside of Visual Studio Code or not before it becoming an available extension. Just a precaution if necessary. Anyway after you have done that you can go back into Visual Studio Code and open a new terminal. In the window of the terminal screen there is a small down arrow that when clicked on will show a menu of other terminal environments you can use. One should be there called Ubuntu (WSL) use this terminal environment and then you can begin following the instructions as outlined in Readme.md. Just so we are clear, I'm not sure if these instructions will actually work for you on you system because of the myriad of setup nuances that may exist on everyone's Windows environment. But the beauty is you have an excellent friend in Chatgpt to help guide you. Hope this helps some of you.
Beta Was this translation helpful? Give feedback.
All reactions