Skip to content

Commit cc81ec0

Browse files
committed
fix image refs
1 parent 96970bf commit cc81ec0

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

docs/docs.trychroma.com/markdoc/content/cloud/sync/github-sync.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -17,26 +17,26 @@ Direct Sync is the default syncing method, which uses the Chroma Cloud GitHub ap
1717

1818
If you do not already have a Chroma Cloud account, you will need to create one at [trychroma.com](https://www.trychroma.com). After creating an account, you can create a database by specifying a name:
1919

20-
{% MarkdocImage lightSrc="/sync/sync_create_database.png" darkSrc="sync/sync_create_database.png" alt="Create database screen" /%}
20+
{% MarkdocImage lightSrc="/sync/sync_create_database.png" darkSrc="/sync/sync_create_database.png" alt="Create database screen" /%}
2121

2222
On the setup screen, select "Sync a GitHub repo":
2323

24-
{% MarkdocImage lightSrc="/sync/sync_new_db_onboarding.png" darkSrc="sync/sync_create_database.png" alt="Onboarding screen for syncing a GitHub repo" /%}
24+
{% MarkdocImage lightSrc="/sync/sync_new_db_onboarding.png" darkSrc="/sync/sync_create_database.png" alt="Onboarding screen for syncing a GitHub repo" /%}
2525

2626
Install the Chroma GitHub App into your GitHub account or organization:
2727

28-
{% MarkdocImage lightSrc="/sync/sync_new_db_github_install.png" darkSrc="sync/sync_new_db_github_install.png" alt="GitHub app installation screen" /%}
28+
{% MarkdocImage lightSrc="/sync/sync_new_db_github_install.png" darkSrc="/sync/sync_new_db_github_install.png" alt="GitHub app installation screen" /%}
2929

3030
And follow the prompts to initiate sync. Choose the **repo** to sync code from, the **branch or commit hash** version of the code to index, and new **collection name** for the synced code. (The collection will be created by the syncing process, and must not exist yet.)
3131

32-
{% MarkdocImage lightSrc="/sync/sync_install.png" darkSrc="sync/sync_install.png" alt="Sync repo to Chroma Collection UI" /%}
32+
{% MarkdocImage lightSrc="/sync/sync_install.png" darkSrc="/sync/sync_install.png" alt="/sync repo to Chroma Collection UI" /%}
3333

3434

3535
3. **Existing database setup**
3636

3737
Open an existing database in Chroma Cloud, and select "Sync" from the menu:
3838

39-
{% MarkdocImage lightSrc="/sync/sync_existing_db.png" darkSrc="/sync/sync_existing_db.png" alt="Sync tab in Chroma Cloud UI" /%}
39+
{% MarkdocImage lightSrc="/sync/sync_existing_db.png" darkSrc="/sync/sync_existing_db.png" alt="/sync tab in Chroma Cloud UI" /%}
4040

4141

4242
On the Sync page, select "Create" to begin syncing code. If you have not already connected GitHub, you may be prompted to install the Chroma Cloud GitHub app again.
@@ -65,21 +65,21 @@ Direct Sync is the default syncing method, which uses the Chroma Cloud GitHub ap
6565

6666
If you do not already have a Chroma Cloud account, you will need to create one at [trychroma.com](https://www.trychroma.com). After creating an account, you can create a database by specifying a name:
6767

68-
{% MarkdocImage lightSrc="/sync/sync_create_database.png" darkSrc="sync/sync_create_database.png" alt="Create database screen" /%}
68+
{% MarkdocImage lightSrc="/sync/sync_create_database.png" darkSrc="/sync/sync_create_database.png" alt="Create database screen" /%}
6969

7070
Once you have a database, you should create an API key to be able to access the Sync Function’s API. You can choose to make this API key scoped to all databases on your account or only the one you just created:
7171

72-
{% MarkdocImage lightSrc="/sync/api_keys.png" darkSrc="sync/api_keys.png" alt="API key issuance for Chroma Cloud" /%}
72+
{% MarkdocImage lightSrc="/sync/api_keys.png" darkSrc="/sync/api_keys.png" alt="API key issuance for Chroma Cloud" /%}
7373

7474
The final setup step is to grant Chroma access to the repositories to which your GitHub App has access. You will need to retrieve the app’s ID and private key from GitHub:
7575

76-
{% MarkdocImage lightSrc="/sync/github_app_id.png" darkSrc="sync/github_app_id.png" alt="GitHub App ID" /%}
76+
{% MarkdocImage lightSrc="/sync/github_app_id.png" darkSrc="/sync/github_app_id.png" alt="GitHub App ID" /%}
7777

78-
{% MarkdocImage lightSrc="/sync/github_secret_key.png" darkSrc="sync/github_secret_key.png" alt="GitHub Secret Key" /%}
78+
{% MarkdocImage lightSrc="/sync/github_secret_key.png" darkSrc="/sync/github_secret_key.png" alt="GitHub Secret Key" /%}
7979

8080
With these credentials, you can use the Chroma dashboard to register your GitHub App with Chroma. **Contact [[email protected]](mailto:[email protected]) for access to this feature.**
8181

82-
{% MarkdocImage lightSrc="/sync/custom-github-app-screen.png" darkSrc="sync/custom-github-app-screen.png" alt="Creating a custom github app" /%}
82+
{% MarkdocImage lightSrc="/sync/custom-github-app-screen.png" darkSrc="/sync/custom-github-app-screen.png" alt="Creating a custom github app" /%}
8383

8484
3. **Creating a source**
8585

@@ -103,7 +103,7 @@ Direct Sync is the default syncing method, which uses the Chroma Cloud GitHub ap
103103

104104
To invoke the Sync Function, you must select a source on which to create the invocation. See the previous step for details on how to create a source. Once you select the source in the UI, you can invoke the Sync Function by clicking “Create invocation”:
105105

106-
{% MarkdocImage lightSrc="/sync/custom_source_invocation.png" darkSrc="sync/custom_source_invocation.png" alt="Creating a custom sync invocation" /%}
106+
{% MarkdocImage lightSrc="/sync/custom_source_invocation.png" darkSrc="/sync/custom_source_invocation.png" alt="Creating a custom sync invocation" /%}
107107

108108
Alternatively, you can invoke the Sync Function by sending an API request to the Sync Function’s API:
109109

0 commit comments

Comments
 (0)