Merge branch 'main' into fix_broken_anchors_1

Author: Blargian

docs/_snippets/_GCS_authentication_and_bucket.md

@@ -1,43 +1,52 @@
 
+import GCS_bucket_1 from '@site/static/images/integrations/data-ingestion/s3/GCS-bucket-1.png';
+import GCS_bucket_2 from '@site/static/images/integrations/data-ingestion/s3/GCS-bucket-2.png';
+import GCS_create_service_account_key from '@site/static/images/integrations/data-ingestion/s3/GCS-create-a-service-account-key.png';
+import GCS_create_service_account_0 from '@site/static/images/integrations/data-ingestion/s3/GCS-create-service-account-0.png';
+import GCS_create_service_account_a from '@site/static/images/integrations/data-ingestion/s3/GCS-create-service-account-a.png';
+import GCS_create_service_account_2 from '@site/static/images/integrations/data-ingestion/s3/GCS-create-service-account-2.png';
+import GCS_create_service_account_3 from '@site/static/images/integrations/data-ingestion/s3/GCS-create-service-account-3.png';
+import GCS_guide_key from '@site/static/images/integrations/data-ingestion/s3/GCS-guide-key.png';
+
 <details>
     <summary>Create GCS buckets and an HMAC key</summary>
 
 ### ch_bucket_us_east1 {#ch_bucket_us_east1}
 
-![Add a bucket](@site/docs/integrations/data-ingestion/s3/images/GCS-bucket-1.png)
+<img src={GCS_bucket_1} alt="Creating a GCS bucket in US East 1" />
 
 ### ch_bucket_us_east4 {#ch_bucket_us_east4}
 
-![Add a bucket](@site/docs/integrations/data-ingestion/s3/images/GCS-bucket-2.png)
+<img src={GCS_bucket_2} alt="Creating a GCS bucket in US East 4" />
 
 ### Generate an Access key {#generate-an-access-key}
 
 ### Create a service account HMAC key and secret {#create-a-service-account-hmac-key-and-secret}
 
 Open **Cloud Storage > Settings > Interoperability** and either choose an existing **Access key**, or **CREATE A KEY FOR A SERVICE ACCOUNT**.  This guide covers the path for creating a new key for a new service account.
 
-![Add a bucket](@site/docs/integrations/data-ingestion/s3/images/GCS-create-a-service-account-key.png)
+<img src={GCS_create_service_account_key} alt="Generating a service account HMAC key in GCS" />
 
 ### Add a new service account {#add-a-new-service-account}
 
 If this is a project with no existing service account, **CREATE NEW ACCOUNT**.
 
-![Add a bucket](@site/docs/integrations/data-ingestion/s3/images/GCS-create-service-account-0.png)
+<img src={GCS_create_service_account_0} alt="Adding a new service account in GCS" />
 
 There are three steps to creating the service account, in the first step give the account a meaningful name, ID, and description.
 
-![Add a bucket](@site/docs/integrations/data-ingestion/s3/images/GCS-create-service-account-a.png)
+<img src={GCS_create_service_account_a} alt="Defining a new service account name and ID in GCS" />
 
 In the Interoperability settings dialog the IAM role **Storage Object Admin** role is recommended; select that role in step two.
 
-![Add a bucket](@site/docs/integrations/data-ingestion/s3/images/GCS-create-service-account-2.png)
+<img src={GCS_create_service_account_2} alt="Selecting IAM role Storage Object Admin in GCS" />
 
 Step three is optional and not used in this guide.  You may allow users to have these privileges based on your policies.
 
-![Add a bucket](@site/docs/integrations/data-ingestion/s3/images/GCS-create-service-account-3.png)
+<img src={GCS_create_service_account_3} alt="Configuring additional settings for the new service account in GCS" />
 
 The service account HMAC key will be displayed.  Save this information, as it will be used in the ClickHouse configuration.
 
-![Add a bucket](@site/docs/integrations/data-ingestion/s3/images/GCS-guide-key.png)
+<img src={GCS_guide_key} alt="Retrieving the generated HMAC key for GCS" />
 
 </details>

docs/_snippets/_S3_authentication_and_bucket.md

@@ -1,3 +1,20 @@
+import s3_1 from '@site/static/images/_snippets/s3/s3-1.png';
+import s3_2 from '@site/static/images/_snippets/s3/s3-2.png';
+import s3_3 from '@site/static/images/_snippets/s3/s3-3.png';
+import s3_4 from '@site/static/images/_snippets/s3/s3-4.png';
+import s3_5 from '@site/static/images/_snippets/s3/s3-5.png';
+import s3_6 from '@site/static/images/_snippets/s3/s3-6.png';
+import s3_7 from '@site/static/images/_snippets/s3/s3-7.png';
+import s3_8 from '@site/static/images/_snippets/s3/s3-8.png';
+import s3_9 from '@site/static/images/_snippets/s3/s3-9.png';
+import s3_a from '@site/static/images/_snippets/s3/s3-a.png';
+import s3_b from '@site/static/images/_snippets/s3/s3-b.png';
+import s3_c from '@site/static/images/_snippets/s3/s3-c.png';
+import s3_d from '@site/static/images/_snippets/s3/s3-d.png';
+import s3_e from '@site/static/images/_snippets/s3/s3-e.png';
+import s3_f from '@site/static/images/_snippets/s3/s3-f.png';
+import s3_g from '@site/static/images/_snippets/s3/s3-g.png';
+import s3_h from '@site/static/images/_snippets/s3/s3-h.png';
 
 <details>
   <summary>Create S3 buckets and an IAM user</summary>
@@ -10,85 +27,85 @@ In this procedure, we'll be creating a service account user, not a login user.
 
 2. In "users", select **Add users**
 
-  ![create_iam_user_0](@site/docs/_snippets/images/s3/s3-1.png)
+<img src={s3_1} alt="create_iam_user_0"/>
 
 3. Enter the user name and set the credential type to **Access key - Programmatic access** and select **Next: Permissions**
 
-  ![create_iam_user_1](@site/docs/_snippets/images/s3/s3-2.png)
+<img src={s3_2} alt="create_iam_user_1"/>
 
 4. Do not add the user to any group; select **Next: Tags**
 
-  ![create_iam_user_2](@site/docs/_snippets/images/s3/s3-3.png)
+<img src={s3_3} alt="create_iam_user_2"/>
 
 5. Unless you need to add any tags, select **Next: Review**
 
-  ![create_iam_user_3](@site/docs/_snippets/images/s3/s3-4.png)
+<img src={s3_4} alt="create_iam_user_3"/>
 
 6. Select **Create User**
 
     :::note
     The warning message stating that the user has no permissions can be ignored; permissions will be granted on the bucket for the user in the next section
     :::
 
-  ![create_iam_user_4](@site/docs/_snippets/images/s3/s3-5.png)
+<img src={s3_5} alt="create_iam_user_4"/>
 
 7. The user is now created; click on **show** and copy the access and secret keys.
 :::note
 Save the keys somewhere else; this is the only time that the secret access key will be available.
 :::
 
-  ![create_iam_user_5](@site/docs/_snippets/images/s3/s3-6.png)
+<img src={s3_6} alt="create_iam_user_5"/>
 
 8. Click close, then find the user in the users screen.
 
-  ![create_iam_user_6](@site/docs/_snippets/images/s3/s3-7.png)
+<img src={s3_7} alt="create_iam_user_6"/>
 
 9. Copy the ARN (Amazon Resource Name) and save it for use when configuring the access policy for the bucket.
 
-  ![create_iam_user_7](@site/docs/_snippets/images/s3/s3-8.png)
+<img src={s3_8} alt="create_iam_user_7"/>
 
 ### Create an S3 bucket {#create-an-s3-bucket}
 1. In the S3 bucket section, select **Create bucket**
 
-  ![create_s3_bucket_0](@site/docs/_snippets/images/s3/s3-9.png)
+<img src={s3_9} alt="create_s3_bucket_0"/>
 
 2. Enter a bucket name, leave other options default
 :::note
 The bucket name must be unique across AWS, not just the organization, or it will emit an error.
 :::
 3. Leave `Block all Public Access` enabled; public access is not needed.
 
-  ![create_s3_bucket_2](@site/docs/_snippets/images/s3/s3-a.png)
+<img src={s3_a} alt="create_s3_bucket_2"/>
 
 4. Select **Create Bucket** at the bottom of the page
 
-  ![create_s3_bucket_3](@site/docs/_snippets/images/s3/s3-b.png)
+<img src={s3_b} alt="create_s3_bucket_3"/>
 
 5. Select the link, copy the ARN, and save it for use when configuring the access policy for the bucket.
 
 6. Once the bucket has been created, find the new S3 bucket in the S3 buckets list and select the link
 
-  ![create_s3_bucket_4](@site/docs/_snippets/images/s3/s3-c.png)
+<img src={s3_c} alt="create_s3_bucket_4"/>
 
 7. Select **Create folder**
 
-  ![create_s3_bucket_5](@site/docs/_snippets/images/s3/s3-d.png)
+<img src={s3_d} alt="create_s3_bucket_5"/>
 
 8. Enter a folder name that will be the target for the ClickHouse S3 disk and select **Create folder**
 
-  ![create_s3_bucket_6](@site/docs/_snippets/images/s3/s3-e.png)
+<img src={s3_e} alt="create_s3_bucket_6"/>
 
 9. The folder should now be visible on the bucket list
 
-  ![create_s3_bucket_7](@site/docs/_snippets/images/s3/s3-f.png)
+<img src={s3_f} alt="create_s3_bucket_7"/>
 
 10. Select the checkbox for the new folder and click on **Copy URL** Save the URL copied to be used in the ClickHouse storage configuration in the next section.
 
-  ![create_s3_bucket_8](@site/docs/_snippets/images/s3/s3-g.png)
+<img src={s3_g} alt="create_s3_bucket_8"/>
 
 11. Select the **Permissions** tab and click on the **Edit** button in the **Bucket Policy** section
 
-  ![create_s3_bucket_9](@site/docs/_snippets/images/s3/s3-h.png)
+<img src={s3_h} alt="create_s3_bucket_9"/>
 
 12. Add a bucket policy, example below:
 ```json

docs/_snippets/_add_remote_ip_access_list_detail.md

@@ -1,13 +1,15 @@
+import ip_allow_list_check_list from '@site/static/images/_snippets/ip-allow-list-check-list.png';
+import ip_allow_list_add_current_ip from '@site/static/images/_snippets/ip-allow-list-add-current-ip.png';
+
 <details>
     <summary>Manage your IP Access List</summary>
 
 From your ClickHouse Cloud services list choose the service that you will work with and switch to **Settings**.  If the IP Access List does not contain the IP Address or range of the remote system that needs to connect to your ClickHouse Cloud service, then you can resolve the problem with **Add IPs**:
 
-![Check to see if the service allows traffic](@site/docs/_snippets/images/ip-allow-list-check-list.png)
+<img src={ip_allow_list_check_list} class="image" alt="Check to see if the service allows traffic" />
 
 Add the individual IP Address, or the range of addresses that need to connect to your ClickHouse Cloud service. Modify the form as you see fit and then **Save**.
 
-![Add your current IP address](@site/docs/_snippets/images/ip-allow-list-add-current-ip.png)
+<img src={ip_allow_list_add_current_ip} class="image" alt="Add your current IP address" />
 
 </details>
-

docs/_snippets/_clickhouse_mysql_cloud_setup.mdx

@@ -1,16 +1,22 @@
+import mysql_1 from '@site/static/images/_snippets/mysql1.png';
+import mysql_2 from '@site/static/images/_snippets/mysql2.png';
+import mysql_3 from '@site/static/images/_snippets/mysql3.png';
+import mysql_4 from '@site/static/images/_snippets/mysql4.png';
+import mysql_5 from '@site/static/images/_snippets/mysql5.png';
+
 <br/>
 1. After creating your ClickHouse Cloud Service, on the `Connect your app` screen, select MySQL from the drop down.
 <br/>
 
 <div class="eighty-percent">
-![Credentials screen - Prompt](./images/mysql1.png)
+    <img src={mysql_1} class="image" alt="Credentials screen - Prompt" />
 </div>
 
-2. Toggle the switch to enable the MySQL interface for this specific service. This will expose port `3306` for this service and prompt you with your MySQL connection screen that include your unique MySQL username. 
 
-<br/>
+2. Toggle the switch to enable the MySQL interface for this specific service. This will expose port `3306` for this service and prompt you with your MySQL connection screen that include your unique MySQL username.
+
 <div class="eighty-percent">
-![Credentials screen - Enabled MySQL](./images/mysql2.png)
+    <img src={mysql_2} class="image" alt="Credentials screen - Enabled MySQL" />
 </div>
 <br/>
 
@@ -20,20 +26,20 @@ Alternatively, in order to enable the MySQL interface for an existing service:
 
 <br/>
 <div class="eighty-percent">
-![Connection screen - Prompt MySQL](./images/mysql3.png)
+    <img src={mysql_3} class="image" alt="Connection screen - Prompt MySQL" />
 </div>
 <br/>
 
 
 4. Select MySQL from the `Connect With` drop down.
 
 <br/>
-![Connection screen - Prompt MySQL](./images/mysql4.png)
+<img src={mysql_4} class="image" alt="Connection screen - Prompt MySQL" />
 <br/>
 
-5. Toggle the switch to enable the MySQL interface for this specific service. This will expose port `3306` for this service and prompt you with your MySQL connection screen that include your unique MySQL username. 
+5. Toggle the switch to enable the MySQL interface for this specific service. This will expose port `3306` for this service and prompt you with your MySQL connection screen that include your unique MySQL username.
 
-![Connection screen -  MySQL Enabled](./images/mysql5.png)
+<img src={mysql_5} class="image" alt="Connection screen - MySQL Enabled" />
 
 ## Creating multiple MySQL users in ClickHouse Cloud {#creating-multiple-mysql-users-in-clickhouse-cloud}
 

docs/_snippets/_gather_your_details_http.mdx

@@ -1,3 +1,6 @@
+import cloud_connect_button from '@site/static/images/_snippets/cloud-connect-button.png';
+import connection_details_https from '@site/static/images/_snippets/connection-details-https.png';
+
 To connect to ClickHouse with HTTP(S) you need this information:
 
 - The HOST and PORT: typically, the port is 8443 when using TLS or 8123 when not using TLS.
@@ -8,10 +11,10 @@ To connect to ClickHouse with HTTP(S) you need this information:
 
 The details for your ClickHouse Cloud service are available in the ClickHouse Cloud console.  Select the service that you will connect to and click **Connect**:
 
-![ClickHouse Cloud service connect button](@site/docs/_snippets/images/cloud-connect-button.png)
+<img src={cloud_connect_button} class="image" alt="ClickHouse Cloud service connect button" />
 
-Choose **HTTPS**, and the details are available in an example `curl` command. 
+Choose **HTTPS**, and the details are available in an example `curl` command.
 
-![ClickHouse Cloud HTTPS connection details](@site/docs/_snippets/images/connection-details-https.png)
+<img src={connection_details_https} class="image" alt="ClickHouse Cloud HTTPS connection details" />
 
 If you are using self-managed ClickHouse, the connection details are set by your ClickHouse administrator.

docs/_snippets/_gather_your_details_native.md

@@ -1,3 +1,6 @@
+import cloud_connect_button from '@site/static/images/_snippets/cloud-connect-button.png';
+import connection_details_native from '@site/static/images/_snippets/connection-details-native.png';
+
 To connect to ClickHouse with native TCP you need this information:
 
 - The HOST and PORT: typically, the port is 9440 when using TLS, or 9000 when not using TLS.
@@ -8,10 +11,10 @@ To connect to ClickHouse with native TCP you need this information:
 
 The details for your ClickHouse Cloud service are available in the ClickHouse Cloud console.  Select the service that you will connect to and click **Connect**:
 
-![ClickHouse Cloud service connect button](@site/docs/_snippets/images/cloud-connect-button.png)
+<img src={cloud_connect_button} class="image" alt="ClickHouse Cloud service connect button" />
 
-Choose **Native**, and the details are available in an example `clickhouse-client` command. 
+Choose **Native**, and the details are available in an example `clickhouse-client` command.
 
-![ClickHouse Cloud Native TCP connection details](@site/docs/_snippets/images/connection-details-native.png)
+<img src={connection_details_native} class="image" alt="ClickHouse Cloud Native TCP connection details" />
 
 If you are using self-managed ClickHouse, the connection details are set by your ClickHouse administrator.

docs/_snippets/_launch_sql_console.md

@@ -1,16 +1,19 @@
+import cloud_connect_to_sql_console from '@site/static/images/_snippets/cloud-connect-to-sql-console.png';
+import createservice8 from '@site/static/images/_snippets/createservice8.png';
+
 :::tip SQL console
 If you need a SQL client connection, your ClickHouse Cloud service has an associated web based SQL console; expand **Connect to SQL console** below for details.
 :::
 
 <details>
     <summary>Connect to SQL console</summary>
 
-From your ClickHouse Cloud services list, click on a service. 
+From your ClickHouse Cloud services list, click on a service.
 
-![Connect to SQL Console](@site/docs/_snippets/images/cloud-connect-to-sql-console.png)
+<img src={cloud_connect_to_sql_console} class="image" alt="Connect to SQL Console" />
 
 This will redirect you to the SQL console.
 
-![SQL Console](@site/docs/_snippets/images/createservice8.png)
+<img src={createservice8} class="image" alt="SQL Console" />
 
 </details>

docs/_snippets/_service_actions_menu.md

@@ -1,3 +1,5 @@
+import cloud_service_action_menu from '@site/static/images/_snippets/cloud-service-actions-menu.png';
+
 Select your service, followed by `Data souces` -> `Predefined sample data`.
 
-![Cloud service Actions menu](@site/docs/_snippets/images/cloud-service-actions-menu.png)
+<img src={cloud_service_action_menu} class="image" alt="Cloud service Actions menu" />

docs/chdb/guides/index.md

@@ -13,3 +13,12 @@ from YAML frontmatter fields title, slug, description. If you've found an error
 in the table of contents, please edit the frontmatter of the files directly.
 -->
 
+| Page | Description |
+|-----|-----|
+| [How to query Parquet files](/docs/chdb/guides/querying-parquet) | Learn how to query Parquet files with chDB. |
+| [How to query data in an S3 bucket](/docs/chdb/guides/querying-s3) | Learn how to query data in an S3 bucket with chDB. |
+| [Using a clickhouse-local database](/docs/chdb/guides/clickhouse-local) | Learn how to use a clickhouse-local database with chDB |
+| [How to query Pandas DataFrames with chDB](/docs/chdb/guides/pandas) | Learn how to query Pandas DataFrames with chDB |
+| [JupySQL and chDB](/docs/chdb/guides/jupysql) | How to install chDB for Bun |
+| [How to query a remote ClickHouse server](/docs/chdb/guides/query-remote-clickhouse) | In this guide, we'll learn how to query a remote ClickHouse server from chDB. |
+| [How to query Apache Arrow with chDB](/docs/chdb/guides/apache-arrow) | In this guide, we'll learn how to query Apache Arrow tables with chDB |