Windows Native Installation and WebGUI Problems.

[gottapro]

I have a working Fabric AI framework running natively on Windows 11.

I used the available binary file. A "fabric --setup" session ran resulting in a ".config" folder in my home directory. It appears to contain a fabric folder with sub-folders for contexts, extensions, patterns, and sessions. Patterns is the only folder populated. I also have a ,env file with the APIs I had input during --setup.

After closing terminal I have no fabric.exe in path, and it appears nowhere on my system! Nothing works. I cannot re-run the binary file unless I delete the .config file and start over!

I install GO and run "go install github.com/danielmiessler/fabric@latest" also from my home directory. This results with a "go" folder in my home directory. Drilling down into it I find the complete fabric install, and with all folders populated. The "web" folder specifically as I ultimately want to get "WebGUI" working.

My "go" folder also has a "bin" folder with fabric.exe, to_pdf.exe, and yt.exe... WOOT WOOT, they are all in my PATH and I can now run fabric from terminal and all feels good.

Now I would like to incorporate the new WebGUI.

I'm limited to the "web" folder inside the "go" folder at:
C:\Users\Jack\go\pkg\mod\github.com\danielmiessler\fabric@v1.4.147\web
Its the only place I find the "web" folder!

Following the installation instructions with execution of "npm install" results in alot of warnings for deprecated packages. The pursuing commands are ugly as well... warns and errors and possible permisson issues?

It devolves from there. I have many hours into trying without luck. I have made some comments in the new WebGUI V2 thread that include additional info.

What am I doing wrong? Am I the first to go for this on windows natively? I may have had more luck with Linux native or even WSL? I thought best performance. and certainly in my case most convenience, would be best achieved in windows natively.

Any thoughts, attention, or advice would be appreciated. Thank you all!

[jmd1010]

Did you clone it as I recommended to you yesterday? If you do, web won't be nested in the go. Let me know if thsat fixed your problem:

Clone the repo (from parent directory)
cd fabric, then go install github.com/danielmiessler/fabric@latest
verify your environment variables as per official README

cd web
npm install
npx svelte-kit sync

Then proceed with your pdf-to-markdown installation: from /web as well
npm install -D patch-package
npm install -D pdfjs-dist@2.5.207
npm install -D github:jzillmann/pdf-to-markdown#modularize

[gottapro]

Yes. I uninstalled everything first. Started with an unmolested home folder.

I git cloned the repo from my home folder... Result was a populated "fabric" folder in said home folder. No fabric.exe was included or entered into my path. This was not unexpected based on prior attempts.

I then entered this "fabric" folder and ran the " go install github.com/danielmiessler/fabric@latest" command from there as you have suggested.

Nothing in the "fabric" folder changed. All time stamps remained unchanged in the "fabric" folder, but a new "go" folder was created in my home folder... just as it had previously.

The go install did give me a working fabric install. The exe files within the go folder are in my PATH, and everything works from a terminal command at this point.

The windows binary install merely gives me a ".config/fabric/" folder... also in my home folder, and this only contains the "patterns" folder and the .env file with APIs and such that I entered into fabric --setup which runs immediately upon execution of the windows binary file provided.

If I follow WebGUI instruction and run the commands from the git pulled "web" folder it does not work. If I try again to run the WebGUI install commands from the "web" folder found drilling down the "go" folder... nothing works.

In summary... It appears the fabric install via binary does not work on its own, but it does give the .config folder containing .env which is utilized once I have executables provided with the extra step of a go install.

Also, in order to run commands referenced in the WebGUI instruction, I had to install NVM and Node.js first. This is not mentioned in any of the installation instructions! I figured this out via additional internet searches outside the provided instruction. All is mute though, as I am unable to get a working WebGUI no matter where or how I'm running the commands.

A clear and concise windows install... from beginning to end... with all steps including dependencies, such as a the go install, Nvm, and node.js installs, appears prudent. No matter what... I do have a working fabric install from a terminal after all these steps, but all seems to run from the "go" folder which does not work for purpose of the WebGUI install.

Thank you for sticking with me on this. Please let me know if any additional info is helpful.

[gottapro]

Here is my ugly prose, previously provided, after using fabric pattern "improve_writing"! :)

Yes. I uninstalled everything first. Started with an unmolested home folder.

I then cloned the repository from my home folder and found a populated "fabric" folder without executables.

Next, I ran the command go install github.com/danielmiessler/fabric@latest within the fabric folder as suggested. Unfortunately, nothing changed in the fabric folder, all timestamps remained unchanged, but a new "go" folder was created in my home folder, and a working fabric installation was achieved through this process.

The windows binary installation resulted only in a ".config/fabric/" folder containing the "patterns" folder and an .env file with APIs. This setup does not work on its own.

When following the WebGUI instructions and running commands from the pulled "web" folder, nothing works. Attempting to run the WebGUI install commands from within the "go" folder found drilling down into it also yielded no results.

In summary, the fabric installation via binary requires an additional step of go install to generate executables in my PATH. Unfortunately, I was unable to get a working WebGUI through any means. Installing NVM and Node.js beforehand is crucial for this setup, but these dependencies are not mentioned in the provided instructions.

A clear and concise windows installation from start to finish, including all necessary steps such as go install, Nvm, and node.js installations, appears prudent. Despite going through multiple steps, my fabric installation runs from the "go" folder, which is not suitable for the WebGUI's purpose.

Thank you for sticking with me on this issue. Please let me know if any additional information can be provided to resolve the problem.

[jmd1010]

That's a bummer. After cloning you should see this folder structure. The right "web" folder to install the GUI is the one circled in red. Sorry not a windows expert. @johnconnor-sec can you help figure this out?

@gottapro if you get an error, ask your llm for help, it may be a very simple thing.

[johnconnor-sec]

You can't run npm (Node Package Manager) without having Node installed. Check the Node downloads page to install Node for Windows. npm is automatically included with Node.js installation.

If you'd like to run the WebUI from Windows, ensure you are installing the npm packages from an administrator powershell or command prompt. Make sure you are installing the npm packages from inside the cloned web/ directory, not the go directory. The go directory is exclusive for Go binaries.

Ensure fabric is in your PATH and run the fabric --serve command to host the GO back-end server.

After npm packages are installed and the fabric server is running, run npm run dev

Installing via WSL2 would be the next easiest fix.

[gottapro]

What did I do:

I copied the git cloned "fabric" folder into the ".config/fabric" folder created when I ran the Windows binary install file (fabric-windows-amd64.exe).

I then followed the WebGUI install instructions from inside the ".config/fabric/web" folder. I had numerous warnings, mostly for deprecated packages, so I ran "npm audit fix --force", which had little to no effect. Instead, I chose to ignore the warnings and proceed with the next commands in the WebGUI installation process, also disregarding any errors or warnings that arose.

Finally, I issued a "fabric --serve" command on the ".config/fabric/web" folder from a terminal. Following this, I ran the "npm dev" command from the same folder in a separate terminal. The WebGUI is now running inside a browser.

I believe it may be functioning as intended; however, more trial will be conducted before declaring complete victory. I'm undoubtedly making some progress!

I believe my install process could be refined? I think I installed Node.js with a windows binary (nvm-setup.exe)?

I may redo all taking @johnconnor-sec advice regarding powershell commands with administrator privilege, but will continue testing what Ive got for now?

I would not have made it this far without input graciously supplied. Thank you all for your attention.