Skip to content
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

Continue Initial documentation assumes Ollama as default #363

Open
yrobla opened this issue Dec 16, 2024 · 2 comments
Open

Continue Initial documentation assumes Ollama as default #363

yrobla opened this issue Dec 16, 2024 · 2 comments

Comments

@yrobla
Copy link
Contributor

yrobla commented Dec 16, 2024

When we see the documentation for Continue integration we just see, by default:

Install a CodeGen model
Download the Code Llama model using Ollama. The following installs the 7 billion parameter (7B) version of the model, which is suitable for systems with 16GB of RAM or more:

ollama pull codellama:7b-instruct

info
If you have at least 32GB of RAM and an 8-core CPU, you can try the 13B parameter model. Replace 7b in these instructions with 13b.

this is just needed for ollama, but is listed in general. I suggest that for Quickstart, we suggest an easier method, such as using the self-hosted in google (or if we really want to use ollama there, give more detailed instructions about how to install it, and mention that this is just one way). Then link to "Use with Continue" section, with the different options there:

Image

Also those tabs should add some instructions/links on how to install each method, dependencies, how to configure api keys etc

@lukehinds
Copy link
Contributor

I think @danbarr is already / had already looked into this

@danbarr
Copy link
Collaborator

danbarr commented Dec 17, 2024

The quickstart is intended to be self-contained, i.e. a first-time user can follow it without requiring any external / paid services, thus the choice to use Ollama. I did add a callout based on other feedback, to hopefully make this more clear and guide users to the full how-to guide for other providers.

Also those tabs should add some instructions/links on how to install each method, dependencies, how to configure api keys etc

I'm hesitant to reproduce documentation for third-party tools that we don't control, we'll be constantly chasing their own changes. Point taken about at least mentioning the dependency, I'll add that with a link to their install docs.

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

No branches or pull requests

3 participants