-
Notifications
You must be signed in to change notification settings - Fork 2
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
issues during setup that I resolved but documenting here #1
Comments
After brew install, did it ask for initial config like below ? which sets the initial config for rye in
and later |
It didn't ask all of those things after installing from brew, only using the bash script that the official website provided did all of that. So I just did that instead. (uninstalling the one from brew first) |
I was able to install rye using brew, but I don't remember it asking questions (it may have, I just don't remember). I do remember having to close terminal and VScode, removing the created virtual environment ( |
I used |
I think the first time you just type |
I had some issues on my mac during the setup process that I wanted to list out here. Probably should put in PR instead of an issue but don't have time
Note: This was the first time I ever used Python on my work laptop
Rye
Don't install
rye
via homebrew, I did and it skipped a few important steps. Install it using the official guide on the website: https://rye-up.com/Allow it to install Python for you and don't forget to "Add Shims to Path": https://rye-up.com/guide/installation/#add-shims-to-path
The install script will prompt you to do it for you, but I said no and did it myself.
Ryn Sync Cert failure
running
rye sync
got me a Cert issue caused by our Zscaler cert.easy fix that I found in our product handbook
I added these variables to my bash/zsh profile (for me it's
.bashrc
)Ollama
I installed this via Homebrew, and then I had to start the service using
brew services start ollama
This command didn't work for me at first
But it worked after I ran
ollama serve
for some reason. See screenshots belowThe text was updated successfully, but these errors were encountered: