mirror of
https://github.com/sourcegraph/sourcegraph.git
synced 2026-02-06 20:31:48 +00:00
[OCT Launch] Docs updates for split Chat/Autocomplete config (#57039)
* Docs updates for split Chat/Autocomplete config * Add small tweaks * Remove new updates
This commit is contained in:
Maedah Batool
GitHub
parent
5851edffb9
commit
315e1a7e38
@ -370,3 +370,7 @@
|
||||
/cody/overview/install-vscode#requirements /cody/overview/install-vscode#prerequisites 308
|
||||
/cody/overview/install-vscode#optional-enable-code-graph-context-for-context-aware-answers /cody/overview/install-vscode#enable-code-graph-context-for-context-aware-answers-optional 308
|
||||
|
||||
# Cody for Enterprise redirects
|
||||
/cody/overview/enable-cody-enterprise#using-a-third-party-llm-provider-directly /cody/overview/enable-cody-enterprise#using-a-third-party-llm-provider 308
|
||||
/cody/overview/enable-cody-enterprise#turning-cody-on-only-for-some-users /cody/overview/enable-cody-enterprise#enable-cody-only-for-some-users 308
|
||||
/cody/overview/enable-cody-enterprise#turning-cody-off /cody/overview/enable-cody-enterprise#disable-cody 308
|
||||
|
||||
@ -1,156 +1,240 @@
|
||||
<style>
|
||||
|
||||
.markdown-body .cards {
|
||||
display: flex;
|
||||
align-items: stretch;
|
||||
}
|
||||
|
||||
.markdown-body .cards .card {
|
||||
flex: 1;
|
||||
margin: 0.5em;
|
||||
color: var(--text-color);
|
||||
border-radius: 4px;
|
||||
border: 1px solid var(--sidebar-nav-active-bg);
|
||||
padding: 1.5rem;
|
||||
padding-top: 1.25rem;
|
||||
}
|
||||
|
||||
.markdown-body .cards .card:hover {
|
||||
color: var(--link-color);
|
||||
}
|
||||
|
||||
.markdown-body .cards .card span {
|
||||
color: var(--link-color);
|
||||
font-weight: bold;
|
||||
}
|
||||
|
||||
.markdown-body .cards {
|
||||
display: flex;
|
||||
align-items: stretch;
|
||||
}
|
||||
|
||||
.markdown-body .cards .card {
|
||||
flex: 1;
|
||||
margin: 0.5em;
|
||||
color: var(--text-color);
|
||||
border-radius: 4px;
|
||||
border: 1px solid var(--sidebar-nav-active-bg);
|
||||
padding: 1.5rem;
|
||||
padding-top: 1.25rem;
|
||||
}
|
||||
|
||||
.markdown-body .cards .card:hover {
|
||||
color: var(--link-color);
|
||||
}
|
||||
|
||||
.markdown-body .cards .card span {
|
||||
color: var(--link-color);
|
||||
font-weight: bold;
|
||||
}
|
||||
|
||||
.limg {
|
||||
list-style: none;
|
||||
margin: 3rem 0 !important;
|
||||
padding: 0 !important;
|
||||
}
|
||||
.limg li {
|
||||
margin-bottom: 1rem;
|
||||
padding: 0 !important;
|
||||
}
|
||||
|
||||
.limg li:last {
|
||||
margin-bottom: 0;
|
||||
}
|
||||
|
||||
.limg a {
|
||||
display: flex;
|
||||
flex-direction: column;
|
||||
transition-property: all;
|
||||
transition-timing-function: cubic-bezier(0.4, 0, 0.2, 1);
|
||||
transition-duration: 350ms;
|
||||
border-radius: 0.75rem;
|
||||
padding-top: 1rem;
|
||||
padding-bottom: 1rem;
|
||||
|
||||
}
|
||||
|
||||
.limg a {
|
||||
padding-left: 1rem;
|
||||
padding-right: 1rem;
|
||||
background: rgb(113 220 232 / 19%);
|
||||
}
|
||||
|
||||
.limg p {
|
||||
margin: 0rem;
|
||||
}
|
||||
.limg a img {
|
||||
width: 1rem;
|
||||
}
|
||||
|
||||
.limg h3 {
|
||||
display:flex;
|
||||
gap: 0.6rem;
|
||||
margin-top: 0;
|
||||
margin-bottom: .25rem
|
||||
|
||||
}
|
||||
</style>
|
||||
|
||||
# Enabling Cody on Sourcegraph Enterprise
|
||||
|
||||
- [Instructions for self-hosted Sourcegraph Enterprise](#cody-on-self-hosted-sourcegraph-enterprise)
|
||||
- [Instructions for Sourcegraph Cloud](#cody-on-sourcegraph-cloud)
|
||||
- [Enabling codebase-aware answers](#enabling-codebase-aware-answers)
|
||||
- [Turning Cody off](#turning-cody-off)
|
||||
<p class="subtitle">Learn how to use Cody and its features with Sourcegraph enterpise.</p>
|
||||
|
||||
## Cody on self-hosted Sourcegraph Enterprise
|
||||
Cody enhances your coding experience by providing intelligent code suggestions, context-aware completions, and advanced code analysis. This guide will walk you through the steps to install and set up Cody with your Sourcegraph enterprise instance via:
|
||||
|
||||
- [Self-hosted Sourcegraph](#cody-on-self-hosted-sourcegraph-enterprise)
|
||||
- [Sourcegraph Cloud](#cody-on-sourcegraph-cloud)
|
||||
|
||||
<ul class="limg">
|
||||
<li>
|
||||
<a class="card text-left" target="_blank" href="https://about.sourcegraph.com/cody/pricing">
|
||||
<h3><img alt="Cody Enterprise" src="https://sourcegraph.com/.assets/img/sourcegraph-mark.svg" />Cody Enterprise</h3>
|
||||
<p>Get in touch with our team to try Cody for Sourcegraph enterprise.</p>
|
||||
</a>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
## Cody on self-hosted Sourcegraph enterprise
|
||||
|
||||
### Prerequisites
|
||||
|
||||
- Sourcegraph 5.1.0 or above
|
||||
- A Sourcegraph Enterprise subscription with [Cody Gateway access](./../explanations/cody_gateway.md), or [an account with a third-party LLM provider](#using-a-third-party-llm-provider-directly).
|
||||
- You have Sourcegraph version 5.1.0 or above
|
||||
- A Sourcegraph enterprise subscription with [Cody Gateway access](./../explanations/cody_gateway.md) or [an account with a third-party LLM provider](#using-a-third-party-llm-provider-directly)
|
||||
|
||||
There are two steps required to enable Cody on your enterprise instance:
|
||||
### Enable Cody on your Sourcegraph instance
|
||||
|
||||
1. Enable Cody on your Sourcegraph instance
|
||||
2. Configure the VS Code extension
|
||||
Cody uses one or more third-party LLM (Large Language Model) providers. Make sure you review [Cody's usage and privacy notice](https://about.sourcegraph.com/terms/cody-notice). Code snippets are sent to a third-party language model provider when you use the Cody extension or enable embeddings.
|
||||
|
||||
### Step 1: Enable Cody on your Sourcegraph instance
|
||||
This requires site-admin privileges. To do so,
|
||||
|
||||
> NOTE: Cody uses one or more third-party LLM (Large Language Model) providers. Make sure you review the [Cody usage and privacy notice](https://about.sourcegraph.com/terms/cody-notice). In particular, code snippets will be sent to a third-party language model provider when you use the Cody extension or when embeddings are enabled.
|
||||
1. First, configure your desired LLM provider either by [Using Sourcegraph Cody Gateway](./../explanations/cody_gateway.md#using-cody-gateway-in-sourcegraph-enterprise) (recommended) or [Using a third-party LLM provider directly](#using-a-third-party-llm-provider-directly)
|
||||
|
||||
This requires site-admin privileges.
|
||||
> NOTE: If you are a Sourcegraph Cloud customer, skip directly to step 3.
|
||||
|
||||
1. First, configure your desired LLM provider:
|
||||
> NOTE: If you are a Sourcegraph Cloud customer, skip to (3).
|
||||
2. Next, go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
|
||||
- Recommended: [Using Sourcegraph Cody Gateway](./../explanations/cody_gateway.md#using-cody-gateway-in-sourcegraph-enterprise)
|
||||
- [Using a third-party LLM provider directly](#using-a-third-party-llm-provider-directly)
|
||||
2. Go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
|
||||
```json
|
||||
```json
|
||||
{
|
||||
// [...]
|
||||
"cody.enabled": true
|
||||
}
|
||||
```
|
||||
3. Set up a policy to automatically create embeddings for repositories: ["Configuring embeddings"](./../explanations/code_graph_context.md#configuring-embeddings)
|
||||
```
|
||||
|
||||
Cody is now fully set up on your instance!
|
||||
3. Finally, set up a policy to automatically [create and configure embeddings](./../explanations/code_graph_context.md#configuring-embeddings) for your repositories.
|
||||
|
||||
### Step 2: Configure the VS Code extension
|
||||
Cody is now fully enabled on your self-hosted Sourcegraph enterprise instance!
|
||||
|
||||
Now that Cody is turned on on your Sourcegraph instance, any user can configure and use the Cody VS Code extension. This does not require admin privilege.
|
||||
### Configure the VS Code extension
|
||||
|
||||
1. If you currently have a previous version of Cody installed, uninstall it and reload VS Code before proceeding to the next steps.
|
||||
2. Search for "Cody AI” in your VS Code extension marketplace, and install it.
|
||||
With Cody enabled on your Sourcegraph instance, any user can configure and use the [Cody VS Code extension](./../overview/install-vscode.md). This does not require admin privilege. However,
|
||||
|
||||
<img width="500" alt="Sourcegraph Cody in VS Code Marketplace" src="https://storage.googleapis.com/sourcegraph-assets/cody-in-marketplace.png">
|
||||
|
||||
3. Reload VS Code, and open the Cody extension. <!-- Review and accept the terms. (this has been removed?) -->
|
||||
|
||||
4. Now you'll need to point the Cody extension to your Sourcegraph instance. Click on "Other Sign In Options..." and select your enterpise option depending on your sourcegraph version (to check your Sourcegraph version go to Sourcegraph => Settings and the version will be in the bottom left)
|
||||
- If you currently installed a previous version of Cody, uninstall it and reload VS Code before proceeding to the next steps
|
||||
- Search for "Cody AI” in your VS Code extension marketplace, and install it again
|
||||
- Reload VS Code, and open the Cody extension <!-- Review and accept the terms. (this has been removed?) -->
|
||||
- Next, to connect the Cody extension with your Sourcegraph instance, click the "Other Sign In Options..." and select your enterprise option depending on your Sourcegraph version (go to **Sourcegraph > Settings**, and the version will be in the bottom left)
|
||||
|
||||
<img width="1369" alt="image" src="https://storage.googleapis.com/sourcegraph-assets/cody-sign-in-options.png">
|
||||
|
||||
5. If you on version 5.1 and above you will just need to follow an authorization flow to give Cody access to your enterpise instance.
|
||||
- If you are on version 5.1 and above, you will need to follow an authorization flow to give Cody access to your enterprise instance
|
||||
- For Sourcegraph 5.0 and above, you'll need to generate an access token. From your Sourcegraph account, go to **Settings > Access tokens** (`https://<your-instance>.sourcegraph.com/users/<your-instance>/settings/tokens`)
|
||||
|
||||
- For Sourcegraph 5.0 and above you'll need to generate an access token. On your Sourcegraph instance, click on **Settings**, then on **Access tokens** (`https://<your-instance>.sourcegraph.com/users/<your-instance>/settings/tokens`). Generate an access token, copy it, and set it in the Cody extension.
|
||||
<img width="1369" alt="image" src="https://user-images.githubusercontent.com/25070988/227510686-4afcb1f9-a3a5-495f-b1bf-6d661ba53cce.png">
|
||||
|
||||
<img width="1369" alt="image" src="https://user-images.githubusercontent.com/25070988/227510686-4afcb1f9-a3a5-495f-b1bf-6d661ba53cce.png">
|
||||
- Create and copy your access token and return to VS code. Once again, click on the "Other Sign In Options..." and select "Sign in to Sourcegraph Enterprise instance via Access Token"
|
||||
- Enter the URL for your sourcegraph instance and then paste in your access token
|
||||
|
||||
- After creating your access token, copy it and return to VS code. Click on the "Other Sign In Options..." button and select "Sign in to Sourcegraph Enterprise instance via Access Token".
|
||||
- Enter the URL for your sourcegraph instance and then paste in your access token.
|
||||
|
||||
<!-- <img width="553" alt="image" src="https://user-images.githubusercontent.com/25070988/227510233-5ce37649-6ae3-4470-91d0-71ed6c68b7ef.png"> -->
|
||||
|
||||
You're all set!
|
||||
|
||||
### Step 3: Try Cody!
|
||||
|
||||
These are a few things you can ask Cody:
|
||||
|
||||
- "What are popular go libraries for building CLIs?"
|
||||
- Open your workspace, and ask "Do we have a React date picker component in this repository?"
|
||||
- Right click on a function, and ask Cody to explain it
|
||||
|
||||
[See more Cody use cases here](./../use-cases.md).
|
||||
You're all set to use Cody on your self-hosted Sourcegraph instance. You can learn more about the Cody use cases [here](./../use-cases.md).
|
||||
|
||||
## Cody on Sourcegraph Cloud
|
||||
|
||||
On [Sourcegraph Cloud](../../cloud/index.md), Cody is a managed service and you do not need to follow step 1 of the self-hosted guide above.
|
||||
|
||||
### Step 1: Enable Cody for your instance
|
||||
|
||||
Cody can be enabled on demand on your Sourcegraph instance by contacting your account manager. The Sourcegraph team will refer to the [handbook](https://handbook.sourcegraph.com/departments/cloud/#managed-instance-requests).
|
||||
|
||||
### Step 2: Configure the VS Code extension
|
||||
[See above](#step-2-configure-the-vs-code-extension).
|
||||
|
||||
### Step 3: Try Cody!
|
||||
[See above](#step-3-try-cody).
|
||||
- With [Sourcegraph Cloud](../../cloud/index.md), you get Cody as a managed service, and you **do not** need to [enable Cody as is required for self-hosted setup](#enable-cody-on-your-sourcegraph-instance)
|
||||
- However, by contacting your account manager, Cody can still be enabled on-demand on your Sourcegraph instance. The Sourcegraph team will refer to the [handbook](https://handbook.sourcegraph.com/departments/cloud/#managed-instance-requests)
|
||||
- Next, you can configure the [VS Code extension](#configure-the-vs-code-extension) by following the same steps as mentioned for the self-hosted environment
|
||||
- After which, you are all set to use Cody with Sourcegraph Cloud
|
||||
|
||||
[Learn more about running Cody on Sourcegraph Cloud](../../cloud/index.md#cody).
|
||||
|
||||
## Enabling codebase-aware answers
|
||||
|
||||
> NOTE: In order to enable codebase-aware answers for Cody, you must first [configure code graph context](./../explanations/code_graph_context.md).
|
||||
> NOTE: To enable codebase-aware answers for Cody, you must first [configure the code graph context](./../explanations/code_graph_context.md).
|
||||
|
||||
The `Cody: Codebase` setting in VS Code enables codebase-aware answers for the Cody extension. By setting this configuration option to the repository name on your Sourcegraph instance, Cody will be able to provide more accurate and relevant answers to your coding questions, based on the context of the codebase you are currently working in.
|
||||
The `Cody: Codebase` setting in VS Code enables codebase-aware answers for the Cody extension.
|
||||
|
||||
1. Open the VS Code workspace settings by pressing <kbd>Cmd/Ctrl+,</kbd>, (or File > Preferences (Settings) on Windows & Linux).
|
||||
2. Search for the `Cody: Codebase` setting.
|
||||
3. Enter the repository name as listed on your Sourcegraph instance.
|
||||
1. For example: `github.com/sourcegraph/sourcegraph` without the `https` protocol
|
||||
- Open your VS Code workspace settings via <kbd>Cmd/Ctrl+,</kbd>, (or File > Preferences (Settings) on Windows & Linux)
|
||||
- Search for the `Cody: Codebase` setting
|
||||
- Enter the repository name as listed in your Sourcegraph instance, for example, `github.com/sourcegraph/sourcegraph` without the `https` protocol
|
||||
|
||||
## Turning Cody off
|
||||
By setting this configuration to the repository name, Cody can provide more accurate and relevant answers to your coding questions based on the context of your current codebase.
|
||||
|
||||
## Disable Cody
|
||||
|
||||
To turn Cody off:
|
||||
|
||||
1. Go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
- Go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
|
||||
```json
|
||||
```json
|
||||
{
|
||||
// [...]
|
||||
"cody.enabled": false
|
||||
}
|
||||
```
|
||||
2. Remove `completions` and `embeddings` configuration if they exist.
|
||||
```
|
||||
|
||||
## Turning Cody on, only for some users
|
||||
- Next, remove `completions` and `embeddings` configuration if they exist
|
||||
|
||||
To turn Cody on only for some users, for example when rolling out a Cody POC, follow all the steps in [Step 1: Enable Cody on your Sourcegraph instance](#step-1-enable-cody-on-your-sourcegraph-instance). Then use the feature flag `cody` to turn Cody on selectively for some users.
|
||||
To do so:
|
||||
## Enable Cody only for some users
|
||||
|
||||
1. Go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
To enable Cody only for some users, for example, when rolling out a Cody POC, follow all the steps mentioned in [Enabling Cody on your Sourcegraph instance](#enable-cody-on-your-sourcegraph-instance). Then, use the feature flag `cody` to turn Cody on selectively for some users. To do so:
|
||||
|
||||
```json
|
||||
- Go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
|
||||
```json
|
||||
{
|
||||
// [...]
|
||||
"cody.enabled": true,
|
||||
"cody.restrictUsersFeatureFlag": true
|
||||
}
|
||||
```
|
||||
1. Go to **Site admin > Feature flags** (`/site-admin/feature-flags`)
|
||||
1. Add a feature flag called `cody`. Select the `boolean` type and set it to `false`.
|
||||
1. Once added, click on the feature flag and use **add overrides** to pick users that will have access to Cody.
|
||||
```
|
||||
|
||||
- Next, go to **Site admin > Feature flags** (`/site-admin/feature-flags`)
|
||||
- Add a feature flag called `cody`
|
||||
- Select the `boolean` type and set it to `false`
|
||||
- Once added, click on the feature flag and use **add overrides** to pick users that will have access to Cody
|
||||
|
||||
<img width="979" alt="Add overides" src="https://user-images.githubusercontent.com/25070988/235454594-9f1a6b27-6882-44d9-be32-258d6c244880.png">
|
||||
|
||||
## Using a third-party LLM provider directly
|
||||
## Using a third-party LLM provider
|
||||
|
||||
Instead of [Sourcegraph Cody Gateway](./../explanations/cody_gateway.md), you can also configure Sourcegraph to use a third-party provider directly, like:
|
||||
|
||||
Instead of [Sourcegraph Cody Gateway](./../explanations/cody_gateway.md), you can configure Sourcegraph to use a third-party provider directly. Currently, this can be one of
|
||||
- Anthropic
|
||||
- OpenAI
|
||||
- Azure OpenAI <span class="badge badge-experimental">Experimental</span>
|
||||
- Azure OpenAI (Experimental)
|
||||
|
||||
### Anthropic
|
||||
|
||||
First, you must create your own key with Anthropic [here](https://console.anthropic.com/account/keys). Once you have the key, go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
Create your own key with Anthropic [here](https://console.anthropic.com/account/keys). Once you have the key, go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
|
||||
```jsonc
|
||||
```json
|
||||
{
|
||||
// [...]
|
||||
"cody.enabled": true,
|
||||
@ -166,9 +250,9 @@ First, you must create your own key with Anthropic [here](https://console.anthro
|
||||
|
||||
### OpenAI
|
||||
|
||||
First, you must create your own key with OpenAI [here](https://beta.openai.com/account/api-keys). Once you have the key, go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
Create your own key with OpenAI [here](https://beta.openai.com/account/api-keys). Once you have the key, go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
|
||||
```jsonc
|
||||
```json
|
||||
{
|
||||
// [...]
|
||||
"cody.enabled": true,
|
||||
@ -182,21 +266,19 @@ First, you must create your own key with OpenAI [here](https://beta.openai.com/a
|
||||
}
|
||||
```
|
||||
|
||||
_[*OpenAI models supported](https://platform.openai.com/docs/models)_
|
||||
[Read and learn more about the supported OpenAI models here →](https://platform.openai.com/docs/models)
|
||||
|
||||
### Azure OpenAI <span class="badge badge-experimental">Experimental</span>
|
||||
### Azure OpenAI <span style="margin-left: 0.25rem" class="badge badge-experimental">Experimental</span>
|
||||
|
||||
> NOTE: Azure OpenAI support is experimental.
|
||||
> NOTE: Azure OpenAI support is in the experimental stage.
|
||||
|
||||
First, make sure you created a project in the Azure OpenAI portal.
|
||||
Create a project in the Azure OpenAI portal. Go to **Keys and Endpoint** from the project overview and get **one of the keys** on that page and the **endpoint**.
|
||||
|
||||
From the project overview, go to **Keys and Endpoint** and grab **one of the keys** on that page, and the **endpoint**.
|
||||
|
||||
Next, under **Model deployments** click "manage deployments" and make sure you deploy the models you want to use. For example, `gpt-35-turbo`. Take note of the **deployment name**.
|
||||
Next, under **Model deployments**, click "manage deployments" and ensure you deploy the models you want, for example, `gpt-35-turbo`. Take note of the **deployment name**.
|
||||
|
||||
Once done, go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
|
||||
```jsonc
|
||||
```json
|
||||
{
|
||||
// [...]
|
||||
"cody.enabled": true,
|
||||
@ -211,18 +293,18 @@ Once done, go to **Site admin > Site configuration** (`/site-admin/configuration
|
||||
}
|
||||
```
|
||||
|
||||
### Anthropic Claude through AWS Bedrock <span class="badge badge-experimental">Experimental</span>
|
||||
### Anthropic Claude through AWS Bedrock <span style="margin-left: 0.25rem" class="badge badge-experimental">Experimental</span>
|
||||
|
||||
> NOTE: AWS Bedrock support is experimental.
|
||||
> NOTE: AWS Bedrock support is in experimental stage.
|
||||
|
||||
First, make sure you have access to AWS Bedrock (currently in beta). Next, request access to the Anthropic Claude models in Bedrock.
|
||||
First, make sure you can access AWS Bedrock (currently in beta). Then, request access to the Anthropic Claude models in Bedrock.
|
||||
This may take some time to provision.
|
||||
|
||||
Next, create an IAM user with programmatic access in your AWS account. Depending on your AWS setup, different ways may be required to provide access. All completions requests are made from the `frontend` service, so this service needs to be able to access AWS. You can either use instance role bindings, or directly configure the IAM user credentials in configuration.
|
||||
Next, create an IAM user with programmatic access in your AWS account. Depending on your AWS setup, different ways may be required to provide access. All completion requests are made from the `frontend` service, so this service needs to be able to access AWS. You can use instance role bindings or directly configure the IAM user credentials in the configuration.
|
||||
|
||||
Once ready, go to **Site admin > Site configuration** (`/site-admin/configuration`) on your instance and set:
|
||||
|
||||
```jsonc
|
||||
```json
|
||||
{
|
||||
// [...]
|
||||
"cody.enabled": true,
|
||||
@ -230,7 +312,6 @@ Once ready, go to **Site admin > Site configuration** (`/site-admin/configuratio
|
||||
"provider": "aws-bedrock",
|
||||
"chatModel": "anthropic.claude-v2",
|
||||
"fastChatModel": "anthropic.claude-instant-v1",
|
||||
"completionModel": "anthropic.claude-instant-v1",
|
||||
"endpoint": "<AWS-Region>", // For example: us-west-2.
|
||||
"accessToken": "<See below>"
|
||||
}
|
||||
@ -238,10 +319,9 @@ Once ready, go to **Site admin > Site configuration** (`/site-admin/configuratio
|
||||
```
|
||||
|
||||
For the access token, you can either:
|
||||
- Leave it empty and rely on instance role bindings or other AWS configurations that are present in the `frontend` service.
|
||||
- Set it to `<ACCESS_KEY_ID>:<SECRET_ACCESS_KEY>` if directly configuring the credentials.
|
||||
- Set it to `<ACCESS_KEY_ID>:<SECRET_ACCESS_KEY>:<SESSION_TOKEN>` if a session token is also required.
|
||||
|
||||
---
|
||||
- Leave it empty and rely on instance role bindings or other AWS configurations in the `frontend` service
|
||||
- Set it to `<ACCESS_KEY_ID>:<SECRET_ACCESS_KEY>` if directly configuring the credentials
|
||||
- Set it to `<ACCESS_KEY_ID>:<SECRET_ACCESS_KEY>:<SESSION_TOKEN>` if a session token is also required
|
||||
|
||||
Similarly, you can also [use a third-party LLM provider directly for embeddings](./../explanations/code_graph_context.md#using-a-third-party-embeddings-provider-directly).
|
||||
|
||||
@ -135,13 +135,13 @@ To start using Cody, pick one of the following:
|
||||
</li>
|
||||
<li>
|
||||
<a class="card text-left" target="_blank" href="https://sourcegraph.com/get-cody">
|
||||
<h3><img alt="VS Code" src="https://storage.googleapis.com/sourcegraph-assets/docs/images/cody/cody-logomark-default.svg"/>Cody App</h3>
|
||||
<h3><img alt="Cody App" src="https://storage.googleapis.com/sourcegraph-assets/docs/images/cody/cody-logomark-default.svg"/>Cody App</h3>
|
||||
<p>Free Cody desktop app to try Cody with your local codebase.</p>
|
||||
</a>
|
||||
</li>
|
||||
<li>
|
||||
<a class="card text-left" target="_blank" href="https://about.sourcegraph.com/cody/pricing">
|
||||
<h3><img alt="JetBrains" src="https://sourcegraph.com/.assets/img/sourcegraph-mark.svg" />Cody Enterprise</h3>
|
||||
<h3><img alt="Cody Enterprise" src="https://sourcegraph.com/.assets/img/sourcegraph-mark.svg" />Cody Enterprise</h3>
|
||||
<p>Get in touch with our team to try Cody for Sourcegraph Enterprise.</p>
|
||||
</a>
|
||||
</li>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user