-
Notifications
You must be signed in to change notification settings - Fork 54
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
Fix Windows Script Issues #70
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The run_cli.sh
also needs to have an additional change of directory to activate the venv
correctly.
As the result of my discussion with @mattigrthr here, we decided to use new approach to the problem by companying shell script entirely with Python script, so those who cannot run a shell script, can use the python script as an alternative. |
Branch conflicts with #71 resolved |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor comments to keep things more concise.
Closing this PR as we replaced the setup scripts with pre-built Docker images and improved documentation for the local Python setup of the CLI (including Windows). The Dockerization of the CLI that would simplify the setup further is in a separate issue #101. |
In this PR, I wanted to add a little fix in 'Windows run-able' script generated by
initialize_windows.sh
by adding some extracd ..
in the second line of each script that needs to be outside of/scripts
folder.