-
Notifications
You must be signed in to change notification settings - Fork 27
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
setup-*.bat broken #378
Comments
Uhm, it generally seems like the Windows Python installer is broken and/or incomplete. |
When you say Windows Python installer, which method is that? Using a pre-installed Python on Windows, or the Windows bundle, or something else? I will fix the If you are running the API server from a clone of the repo, you may need to build or download the GUI files as well. You can grab a copy from the The Windows bundle comes with the GUI files, but if you cloned the repo, they will be missing. Download (or build and copy) them into https://github.com/ssube/onnx-web/tree/main/api/gui, and that should work. |
There were at least two parts to this, and I believe both are now fixed:
I was hoping to add the GUI download to the launch script, but it looks like that might only work reliably within powershell (https://stackoverflow.com/questions/4619088/windows-batch-file-file-download-from-a-url), so that's covered in the setup documentation for now. |
The launch.bat script now has a check for the web UI files and the launch.ps1 script will check for and download them if they are not found. |
The
setup-*.bat
files inapi/
just callonnx_env\Scripts\activate.bat
in line 2, which will terminate the script after calling the activate script.Instead they must
call
the activate script, e.g. like thiscall onnx_env\Scripts\activate.bat
to continue and perform the following commands.Also the setup guide for Windows is somewhat incomplete, as it does not mention that the
setup-*.bat
files can be found inapi/
.The text was updated successfully, but these errors were encountered: