Merge pull request #3408 from Blargian/move_images_to_static

move images to static

Author: gingerwizard

docs/integrations/data-ingestion/clickpipes/postgres/index.md

@@ -7,7 +7,12 @@ slug: /integrations/clickpipes/postgres
 import BetaBadge from '@theme/badges/BetaBadge';
 import cp_service from '@site/static/images/integrations/data-ingestion/clickpipes/cp_service.png';
 import cp_step0 from '@site/static/images/integrations/data-ingestion/clickpipes/cp_step0.png';
-
+import postgres_tile from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/postgres-tile.jpg'
+import postgres_connection_details from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/postgres-connection-details.jpg'
+import ssh_tunnel from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/ssh-tunnel.jpg'
+import select_replication_slot from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/select-replication-slot.jpg'
+import select_destination_db from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/select-destination-db.jpg'
+import ch_permissions from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/ch-permissions.jpg'
 
 # Ingesting Data from Postgres to ClickHouse (using CDC)
 
@@ -63,7 +68,7 @@ Make sure you are logged in to your ClickHouse Cloud account. If you don't have
 
 3. Select the `Postgres CDC` tile
 
-   ![Select Postgres](./images/postgres-tile.jpg)
+   <img src={postgres_tile} alt="Select Postgres" />
 
 ### Adding your source Postgres database connection {#adding-your-source-postgres-database-connection}
 
@@ -76,16 +81,17 @@ Make sure you are logged in to your ClickHouse Cloud account. If you don't have
 
    :::
 
-   ![Fill in connection details](./images/postgres-connection-details.jpg)
+   <img src={postgres_connection_details} alt="Fill in connection details" />
 
 #### (Optional) Setting up SSH Tunneling {#optional-setting-up-ssh-tunneling}
 
 You can specify SSH tunneling details if your source Postgres database is not publicly accessible.
 
+
 1. Enable the "Use SSH Tunnelling" toggle.
 2. Fill in the SSH connection details.
 
-   ![SSH tunneling](./images/ssh-tunnel.jpg)
+   <img src={ssh_tunnel} alt="SSH tunneling" />
 
 3. To use Key-based authentication, click on "Revoke and generate key pair" to generate a new key pair and copy the generated public key to your SSH server under `~/.ssh/authorized_keys`.
 4. Click on "Verify Connection" to verify the connection.
@@ -102,7 +108,7 @@ Once the connection details are filled in, click on "Next".
 
 5. Make sure to select the replication slot from the dropdown list you created in the prerequisites step.
 
-   ![Select replication slot](./images/select-replication-slot.jpg)
+   <img src={select_replication_slot} alt="Select replication slot" />
 
 #### Advanced Settings {#advanced-settings}
 
@@ -119,8 +125,8 @@ You can configure the Advanced settings if needed. A brief description of each s
 
 6. Here you can select the destination database for your ClickPipe. You can either select an existing database or create a new one.
 
-   ![Select destination database](./images/select-destination-db.jpg)
-
+   <img src={select_destination_db} alt="Select destination database" />
+   
 7. You can select the tables you want to replicate from the source Postgres database. While selecting the tables, you can also choose to rename the tables in the destination ClickHouse database as well as exclude specific columns.
 
    :::warning
@@ -133,8 +139,7 @@ You can configure the Advanced settings if needed. A brief description of each s
 
 8. Select the "Full access" role from the permissions dropdown and click "Complete Setup".
 
-   ![Review permissions](./images/ch-permissions.jpg)
-
+   <img src={ch_permissions} alt="Review permissions" />
 
 ## What's next? {#whats-next}
 

docs/integrations/data-ingestion/clickpipes/postgres/source/crunchy-postgres.md

@@ -4,6 +4,9 @@ description: Set up Crunchy Bridge Postgres as a source for ClickPipes
 slug: /integrations/clickpipes/postgres/source/crunchy-postgres
 ---
 
+import firewall_rules_crunchy_bridge from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/crunchy-postgres/firewall_rules_crunchy_bridge.png'
+import add_firewall_rules_crunchy_bridge from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/crunchy-postgres/add_firewall_rules_crunchy_bridge.png'
+
 # Crunchy Bridge Postgres Source Setup Guide
 
 
@@ -53,10 +56,9 @@ Connect to your Crunchy Bridge Postgres through the `postgres` user and run the
 
 Safelist [ClickPipes IPs](../../index.md#list-of-static-ips) by adding the Firewall Rules in Crunchy Bridge.
 
-![Where to find Firewall Rules in Crunchy Bridge?](images/setup/crunchy-postgres/firewall_rules_crunchy_bridge.png)
-
-![Add the Firewall Rules for ClickPipes](images/setup/crunchy-postgres/add_firewall_rules_crunchy_bridge.png)
+<img src={firewall_rules_crunchy_bridge} alt="Where to find Firewall Rules in Crunchy Bridge?"/>
 
+<img src={add_firewall_rules_crunchy_bridge} alt="Add the Firewall Rules for ClickPipes"/>
 
 
 

docs/integrations/data-ingestion/clickpipes/postgres/source/neon-postgres.md

@@ -4,19 +4,25 @@ description: Set up Neon Postgres instance as a source for ClickPipes
 slug: /integrations/clickpipes/postgres/source/neon-postgres
 ---
 
+import neon_commands from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/neon-postgres/neon-commands.png'
+import neon_enable_replication from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/neon-postgres/neon-enable-replication.png'
+import neon_enabled_replication from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/neon-postgres/neon-enabled-replication.png'
+import neon_ip_allow from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/neon-postgres/neon-ip-allow.png'
+import neon_conn_details from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/neon-postgres/neon-conn-details.png'
+
 # Neon Postgres Source Setup Guide
 
 This is a guide on how to setup Neon Postgres, which you can use for replication in ClickPipes.
 Make sure you're signed in to your [Neon console](https://console.neon.tech/app/projects) for this setup.
 
-
 ## Creating a user with permissions {#creating-a-user-with-permissions}
 
 Let's create a new user for ClickPipes with the necessary permissions suitable for CDC,
 and also create a publication that we'll use for replication.
 
 For this, you can head over to the **SQL Console** tab.
 Here, we can run the following SQL commands:
+
 ```sql
   CREATE USER clickpipes_user PASSWORD 'clickpipes_password';
   GRANT USAGE ON SCHEMA "public" TO clickpipes_user;
@@ -30,21 +36,19 @@ Here, we can run the following SQL commands:
   CREATE PUBLICATION clickpipes_publication FOR ALL TABLES;
 ```
 
-![User and publication commands](images/setup/neon-postgres/neon-commands.png)
-
+<img src={neon_commands} alt="User and publication commands"/>
 
 Click on **Run** to have a publication and a user ready.
 
 ## Enable Logical Replication {#enable-logical-replication}
 In Neon, you can enable logical replication through the UI. This is necessary for ClickPipes's CDC to replicate data.
 Head over to the **Settings** tab and then to the **Logical Replication** section.
 
-![Enable logical replication](images/setup/neon-postgres/neon-enable-replication.png)
+<img src={neon_enable_replication} alt="Enable logical replication"/>
 
 Click on **Enable** to be all set here. You should see the below success message once you enable it.
 
-![Logical replication enabled](images/setup/neon-postgres/neon-enabled-replication.png)
-
+<img src={neon_enabled_replication} alt="Logical replication enabled"/>
 
 Let's verify the below settings in your Neon Postgres instance:
 ```sql
@@ -53,24 +57,18 @@ SHOW max_wal_senders; -- should be 10
 SHOW max_replication_slots; -- should be 10
 ```
 
-
 ## IP Whitelisting (For Neon Enterprise plan) {#ip-whitelisting-for-neon-enterprise-plan}
 If you have Neon Enterprise plan, you can whitelist the [ClickPipes IPs](../../index.md#list-of-static-ips) to allow replication from ClickPipes to your Neon Postgres instance.
 To do this you can click on the **Settings** tab and go to the **IP Allow** section.
 
-![Allow IPs screen](images/setup/neon-postgres/neon-ip-allow.png)
-
+<img src={neon_ip_allow} alt="Allow IPs screen"/>
 
 ## Copy Connection Details {#copy-connection-details}
 Now that we have the user, publication ready and replication enabled, we can copy the connection details to create a new ClickPipe.
 Head over to the **Dashboard** and at the text box where it shows the connection string,
 change the view to **Parameters Only**. We will need these parameters for our next step.
 
-![Connection details](images/setup/neon-postgres/neon-conn-details.png)
-
-
-
-
+<img src={neon_conn_details} alt="Connection details"/>
 
 ## What's next? {#whats-next}
 

docs/integrations/data-ingestion/clickpipes/postgres/source/supabase.md

@@ -4,6 +4,9 @@ description: Set up Supabase instance as a source for ClickPipes
 slug: /integrations/clickpipes/postgres/source/supabase
 ---
 
+import supabase_commands from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/supabase/supabase-commands.jpg'
+import supabase_connection_details from '@site/static/images/integrations/data-ingestion/clickpipes/postgres/source/setup/supabase/supabase-connection-details.jpg' 
+
 # Supabase Source Setup Guide
 
 This is a guide on how to setup Supabase Postgres for usage in ClickPipes.
@@ -35,8 +38,7 @@ Here, we can run the following SQL commands:
   CREATE PUBLICATION clickpipes_publication FOR ALL TABLES;
 ```
 
-![User and publication commands](images/setup/supabase/supabase-commands.jpg)
-
+<img src={supabase_commands} alt="User and publication commands"/>
 
 
 Click on **Run** to have a publication and a user ready.
@@ -69,8 +71,7 @@ Head over to your Supabase Project's `Project Settings` -> `Database` (under `Co
 
 **Important**: Disable `Display connection pooler` on this page and head over to the `Connection parameters` section and note/copy the parameters.
 
-![Locate Supabase Connection Details](images/setup/supabase/supabase-connection-details.jpg)
-
+<img src={supabase_connection_details} alt="Locate Supabase Connection Details"/>
 
 :::info
 

docs/integrations/data-ingestion/dbms/dynamodb/index.md

@@ -8,6 +8,9 @@ keywords: [clickhouse, DynamoDB, connect, integrate, table]
 
 import CloudNotSupportedBadge from '@theme/badges/CloudNotSupportedBadge';
 import ExperimentalBadge from '@theme/badges/ExperimentalBadge';
+import dynamodb_kinesis_stream from '@site/static/images/integrations/data-ingestion/dbms/dynamodb/dynamodb-kinesis-stream.png';
+import dynamodb_s3_export from '@site/static/images/integrations/data-ingestion/dbms/dynamodb/dynamodb-s3-export.png';
+import dynamodb_map_columns from '@site/static/images/integrations/data-ingestion/dbms/dynamodb/dynamodb-map-columns.png';
 
 # CDC from DynamoDB to ClickHouse
 
@@ -27,14 +30,14 @@ Data will be ingested into a `ReplacingMergeTree`. This table engine is commonly
 First, you will want to enable a Kinesis stream on your DynamoDB table to capture changes in real-time. We want to do this before we create the snapshot to avoid missing any data.
 Find the AWS guide located [here](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/kds.html).
 
-![DynamoDB Kinesis Stream](../images/dynamodb-kinesis-stream.png)
+<img src={dynamodb_kinesis_stream} alt="DynamoDB Kinesis Stream"/>
 
 ## 2. Create the snapshot {#2-create-the-snapshot}
 
 Next, we will create a snapshot of the DynamoDB table. This can be achieved through an AWS export to S3. Find the AWS guide located [here](https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/S3DataExport.HowItWorks.html).
 **You will want to do a "Full export" in the DynamoDB JSON format.**
 
-![DynamoDB S3 Export](../images/dynamodb-s3-export.png)
+<img src={dynamodb_s3_export} alt="DynamoDB S3 Export"/>
 
 ## 3. Load the snapshot into ClickHouse {#3-load-the-snapshot-into-clickhouse}
 
@@ -124,8 +127,7 @@ Now we can set up the Kinesis ClickPipe to capture real-time changes from the Ki
   - `ApproximateCreationDateTime`: `version`
   - Map other fields to the appropriate destination columns as shown below
 
-![DynamoDB Map Columns](../images/dynamodb-map-columns.png) 
-
+<img src={dynamodb_map_columns} alt="DynamoDB Map Columns"/>
 
 ## 5. Cleanup (optional) {#5-cleanup-optional}
 

docs/integrations/data-ingestion/dbms/jdbc-with-clickhouse.md

@@ -8,6 +8,9 @@ description: The ClickHouse JDBC Bridge allows ClickHouse to access data from an
 
 import Tabs from '@theme/Tabs';
 import TabItem from '@theme/TabItem';
+import Jdbc01 from '@site/static/images/integrations/data-ingestion/dbms/jdbc-01.png';
+import Jdbc02 from '@site/static/images/integrations/data-ingestion/dbms/jdbc-02.png';
+import Jdbc03 from '@site/static/images/integrations/data-ingestion/dbms/jdbc-03.png';
 
 # Connecting ClickHouse to external data sources with JDBC
 
@@ -16,7 +19,7 @@ Using JDBC requires the ClickHouse JDBC bridge, so you will need to use `clickho
 :::
 
 **Overview:** The <a href="https://github.com/ClickHouse/clickhouse-jdbc-bridge" target="_blank">ClickHouse JDBC Bridge</a> in combination with the [jdbc table function](/sql-reference/table-functions/jdbc.md) or the [JDBC table engine](/engines/table-engines/integrations/jdbc.md) allows ClickHouse to access data from any external data source for which a <a href="https://en.wikipedia.org/wiki/JDBC_driver" target="_blank">JDBC driver</a> is available:
-<img src={require('./images/jdbc-01.png').default} class="image" alt="ClickHouse JDBC Bridge"/>
+<img src={Jdbc01} class="image" alt="ClickHouse JDBC Bridge"/>
 This is handy when there is no native built-in [integration engine](/engines/table-engines/index.md#integration-engines-integration-engines), table function, or external dictionary for the external data source available, but a JDBC driver for the data source exists.
 
 You can use the ClickHouse JDBC Bridge for both reads and writes. And in parallel for multiple external data sources, e.g. you can run distributed queries on ClickHouse across multiple external and internal data sources in real time.
@@ -36,7 +39,7 @@ You have access to a machine that has:
 
 ## Install the ClickHouse JDBC Bridge locally {#install-the-clickhouse-jdbc-bridge-locally}
 
-The easiest way to use the ClickHouse JDBC Bridge is to install and run it on the same host where also ClickHouse is running:<img src={require('./images/jdbc-02.png').default} class="image" alt="ClickHouse JDBC Bridge locally"/>
+The easiest way to use the ClickHouse JDBC Bridge is to install and run it on the same host where also ClickHouse is running:<img src={Jdbc02} class="image" alt="ClickHouse JDBC Bridge locally"/>
 
 Let's start by connecting to the Unix shell on the machine where ClickHouse is running and create a local folder where we will later install the ClickHouse JDBC Bridge into (feel free to name the folder anything you like and put it anywhere you like):
 ```bash
@@ -137,7 +140,7 @@ As the first parameter for the jdbc table function we are using the name of the
 ## Install the ClickHouse JDBC Bridge externally {#install-the-clickhouse-jdbc-bridge-externally}
 
 For a distributed ClickHouse cluster (a cluster with more than one ClickHouse host) it makes sense to install and run the ClickHouse JDBC Bridge externally on its own host:
-<img src={require('./images/jdbc-03.png').default} class="image" alt="ClickHouse JDBC Bridge externally"/>
+<img src={Jdbc03} class="image" alt="ClickHouse JDBC Bridge externally"/>
 This has the advantage that each ClickHouse host can access the JDBC Bridge. Otherwise the JDBC Bridge would need to be installed locally for each ClickHouse instance that is supposed to access external data sources via the Bridge.
 
 In order to install the ClickHouse JDBC Bridge externally, we do the following steps:

docs/integrations/data-ingestion/dbms/postgresql/postgres-vs-clickhouse.md

@@ -4,6 +4,8 @@ title: Comparing PostgreSQL and ClickHouse
 keywords: [postgres, postgresql, comparison]
 ---
 
+import postgresReplicas from '@site/static/images/integrations/data-ingestion/dbms/postgres-replicas.png';
+
 ## Postgres vs ClickHouse: Equivalent and different concepts {#postgres-vs-clickhouse-equivalent-and-different-concepts}
 
 Users coming from OLTP systems who are used to ACID transactions should be aware that ClickHouse makes deliberate compromises in not fully providing these in exchange for performance. ClickHouse semantics can deliver high durability guarantees and high write throughput if well understood. We highlight some key concepts below that users should be familiar with prior to working with ClickHouse from Postgres.
@@ -32,7 +34,7 @@ The replication process in ClickHouse (1) starts when data is inserted into any
 
 <br />
 
-<img src={require('../images/postgres-replicas.png').default}    
+<img src={postgresReplicas}    
   class="image"
   alt="NEEDS ALT"
   style={{width: '500px'}} />

docs/integrations/data-ingestion/etl-tools/dbt/index.md

@@ -67,7 +67,8 @@ pip install dbt-clickhouse
 
 dbt excels when modeling highly relational data. For the purposes of example, we provide a small IMDB dataset with the following relational schema. This dataset originates from the[ relational dataset repository](https://relational.fit.cvut.cz/dataset/IMDb). This is trivial relative to common schemas used with dbt but represents a manageable sample:
 
-<img src={dbt_01} class="image" alt="IMDB table schema" style={{width: '100%'}} />
+
+<img src={dbt_01} class="image" alt="IMDB table schema" style={{width: '100%'}}/>
 
 We use a subset of these tables as shown.
 

docs/integrations/data-ingestion/google-dataflow/templates.md

@@ -9,9 +9,6 @@ description: Users can ingest data into ClickHouse using Google Dataflow Templat
 
 Google Dataflow templates provide a convenient way to execute prebuilt, ready-to-use data pipelines without the need to write custom code. These templates are designed to simplify common data processing tasks and are built using [Apache Beam](https://beam.apache.org/), leveraging connectors like `ClickHouseIO` for seamless integration with ClickHouse databases. By running these templates on Google Dataflow, you can achieve highly scalable, distributed data processing with minimal effort.
 
-
-
-
 ## Why Use Dataflow Templates? {#why-use-dataflow-templates}
 
 - **Ease of Use**: Templates eliminate the need for coding by offering preconfigured pipelines tailored to specific use cases.

docs/integrations/data-ingestion/google-dataflow/templates/bigquery-to-clickhouse.md

@@ -6,6 +6,7 @@ description: Users can ingest data from BigQuery into ClickHouse using Google Da
 ---
 
 import TOCInline from '@theme/TOCInline';
+import dataflow_inqueue_job from '@site/static/images/integrations/data-ingestion/google-dataflow/dataflow-inqueue-job.png'
 
 # Dataflow BigQuery to ClickHouse template
 
@@ -136,8 +137,7 @@ job:
 Navigate to the [Dataflow Jobs tab](https://console.cloud.google.com/dataflow/jobs) in your Google Cloud Console to
 monitor the status of the job. You’ll find the job details, including progress and any errors:
 
-<img src={require('../images/dataflow-inqueue-job.png').default} class="image" alt="DataFlow running job"
-style={{width: '100%', 'background-color': 'transparent'}}/>
+<img src={dataflow_inqueue_job} class="image" alt="DataFlow running job" style={{width: '100%', 'background-color': 'transparent'}}/>
 
 ## Troubleshooting {#troubleshooting}