8000 fix: I needed to run ollama serve first, fix: put route in for vite ping by bettlebrox · Pull Request #1 · dgurns/second-opinion · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fix: I needed to run ollama serve first, fix: put route in for vite ping #1

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

bettlebrox
Copy link

No description provided.

Copy link
Owner
@dgurns dgurns left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Appreciate the PR @bettlebrox!!
Just a question on the readme

@@ -19,13 +19,14 @@ cp .env.sample .env
2. Download the local LLM and serve it via Ollama:

```bash
# start ollama so you can pull the model
# Or run the Ollama desktop app to serve automatically
ollama serve
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't you have to pull the model first before serving it?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think serve is just to start ollama. I don't have the desktop app so if I don't start ollama I can't pull.

image

@@ -6,4 +6,5 @@ export default [
route("/second-opinion", "routes/second-opinion.tsx"),
route("/clear-details", "routes/clear-details.tsx"),
route("/delete-detail", "routes/delete-detail.tsx"),
route("/__vite_ping", "routes/noop.tsx")
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the purpose of this route? Would have assumed any kind of internal Vite healthcheck is handled by the Vite dev server itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0