Re-add optimized versions of .png images

For optimizing the images, `oxipng` has been used. oxipng --opt 6 *
crate · Oct 26, 2023 · 9c6e3bc · 9c6e3bc
1 parent 26b0b50
commit 9c6e3bc
Show file tree

Hide file tree

Showing 64 changed files with 59 additions and 59 deletions.
diff --git a/docs/_assets/img/getting-started/create-user.png b/docs/_assets/img/getting-started/create-user.png
diff --git a/docs/_assets/img/getting-started/first-use/admin-ui.png b/docs/_assets/img/getting-started/first-use/admin-ui.png
diff --git a/docs/_assets/img/getting-started/generate-time-series/map.png b/docs/_assets/img/getting-started/generate-time-series/map.png
diff --git a/docs/_assets/img/getting-started/generate-time-series/rows.png b/docs/_assets/img/getting-started/generate-time-series/rows.png
diff --git a/docs/_assets/img/getting-started/generate-time-series/table.png b/docs/_assets/img/getting-started/generate-time-series/table.png
diff --git a/docs/_assets/img/getting-started/normalize-intervals/data-24h-more.png b/docs/_assets/img/getting-started/normalize-intervals/data-24h-more.png
diff --git a/docs/_assets/img/getting-started/normalize-intervals/data-24h.png b/docs/_assets/img/getting-started/normalize-intervals/data-24h.png
diff --git a/docs/_assets/img/getting-started/normalize-intervals/data-by-minute.png b/docs/_assets/img/getting-started/normalize-intervals/data-by-minute.png
diff --git a/docs/_assets/img/getting-started/normalize-intervals/jupyter-hello-world.png b/docs/_assets/img/getting-started/normalize-intervals/jupyter-hello-world.png
diff --git a/docs/_assets/img/getting-started/normalize-intervals/null-by-minute-24h.png b/docs/_assets/img/getting-started/normalize-intervals/null-by-minute-24h.png
diff --git a/docs/_assets/img/getting-started/normalize-intervals/orbit.png b/docs/_assets/img/getting-started/normalize-intervals/orbit.png
diff --git a/docs/_assets/img/getting-started/normalize-intervals/raw-data.png b/docs/_assets/img/getting-started/normalize-intervals/raw-data.png
diff --git a/docs/_assets/img/integrations/azfunc.png b/docs/_assets/img/integrations/azfunc.png
diff --git a/docs/_assets/img/integrations/kafka-connect.png b/docs/_assets/img/integrations/kafka-connect.png
diff --git a/docs/_assets/img/integrations/mlp_model_train_loss.png b/docs/_assets/img/integrations/mlp_model_train_loss.png
diff --git a/docs/_assets/img/integrations/powerbi-connection-successful.png b/docs/_assets/img/integrations/powerbi-connection-successful.png
diff --git a/docs/_assets/img/integrations/powerbi-crate-dsn.png b/docs/_assets/img/integrations/powerbi-crate-dsn.png
diff --git a/docs/_assets/img/integrations/powerbi-driver-select.png b/docs/_assets/img/integrations/powerbi-driver-select.png
diff --git a/docs/_assets/img/integrations/powerbi-dsn-setup.png b/docs/_assets/img/integrations/powerbi-dsn-setup.png
diff --git a/docs/_assets/img/integrations/powerbi-gateway-clusters.png b/docs/_assets/img/integrations/powerbi-gateway-clusters.png
diff --git a/docs/_assets/img/integrations/powerbi-gateway-connection.png b/docs/_assets/img/integrations/powerbi-gateway-connection.png
diff --git a/docs/_assets/img/integrations/powerbi-gateway-status.png b/docs/_assets/img/integrations/powerbi-gateway-status.png
diff --git a/docs/_assets/img/integrations/powerbi-manage-gateways.png b/docs/_assets/img/integrations/powerbi-manage-gateways.png
diff --git a/docs/_assets/img/integrations/powerbi-pie-chart.png b/docs/_assets/img/integrations/powerbi-pie-chart.png
diff --git a/docs/_assets/img/integrations/powerbi-postgres-drivers.png b/docs/_assets/img/integrations/powerbi-postgres-drivers.png
diff --git a/docs/_assets/img/integrations/powerbi-publish-destination.png b/docs/_assets/img/integrations/powerbi-publish-destination.png
diff --git a/docs/_assets/img/integrations/powerbi-publish-success.png b/docs/_assets/img/integrations/powerbi-publish-success.png
diff --git a/docs/_assets/img/integrations/powerbi-published-report.png b/docs/_assets/img/integrations/powerbi-published-report.png
diff --git a/docs/_assets/img/integrations/powerbi-refresh-in-progress.png b/docs/_assets/img/integrations/powerbi-refresh-in-progress.png
diff --git a/docs/_assets/img/integrations/powerbi-refresh-now.png b/docs/_assets/img/integrations/powerbi-refresh-now.png
diff --git a/docs/_assets/img/integrations/powerbi-refreshed-report.png b/docs/_assets/img/integrations/powerbi-refreshed-report.png
diff --git a/docs/_assets/img/integrations/powerbi-schedule-refresh.png b/docs/_assets/img/integrations/powerbi-schedule-refresh.png
diff --git a/docs/_assets/img/integrations/powerbi-source.png b/docs/_assets/img/integrations/powerbi-source.png
diff --git a/docs/_assets/img/integrations/powerbi-start-menu.png b/docs/_assets/img/integrations/powerbi-start-menu.png
diff --git a/docs/_assets/img/integrations/powerbi-table-navigator.png b/docs/_assets/img/integrations/powerbi-table-navigator.png
diff --git a/docs/_assets/img/integrations/r-iris-features.png b/docs/_assets/img/integrations/r-iris-features.png
diff --git a/docs/_assets/img/integrations/streamsets-directory-files.png b/docs/_assets/img/integrations/streamsets-directory-files.png
diff --git a/docs/_assets/img/integrations/streamsets-directory-format.png b/docs/_assets/img/integrations/streamsets-directory-format.png
diff --git a/docs/_assets/img/integrations/streamsets-field-type-conversions.png b/docs/_assets/img/integrations/streamsets-field-type-conversions.png
diff --git a/docs/_assets/img/integrations/streamsets-jdbc-driver.png b/docs/_assets/img/integrations/streamsets-jdbc-driver.png
diff --git a/docs/_assets/img/integrations/streamsets-jdbc-producer-credentials.png b/docs/_assets/img/integrations/streamsets-jdbc-producer-credentials.png
diff --git a/docs/_assets/img/integrations/streamsets-jdbc-producer-settings.png b/docs/_assets/img/integrations/streamsets-jdbc-producer-settings.png
diff --git a/docs/_assets/img/integrations/streamsets-new-pipeline.png b/docs/_assets/img/integrations/streamsets-new-pipeline.png
diff --git a/docs/_assets/img/integrations/streamsets-pipeline.png b/docs/_assets/img/integrations/streamsets-pipeline.png
diff --git a/docs/_assets/img/integrations/streamsets-running-pipeline.png b/docs/_assets/img/integrations/streamsets-running-pipeline.png
diff --git a/docs/_assets/img/multi-node-cluster.png b/docs/_assets/img/multi-node-cluster.png
diff --git a/docs/_assets/img/reference-architectures/cratedb-azure-iot.png b/docs/_assets/img/reference-architectures/cratedb-azure-iot.png
diff --git a/docs/_assets/img/reference-architectures/distributed-ml.png b/docs/_assets/img/reference-architectures/distributed-ml.png
diff --git a/docs/getting-started/create-user.rst b/docs/getting-started/create-user.rst
@@ -51,7 +51,7 @@ Grant all privileges to the newly created user:
 
    cr> GRANT ALL PRIVILEGES TO username;
 
-.. image:: _assets/img/create-user.png
+.. image:: /_assets/img/getting-started/create-user.png
 
 Now try navigating to the :ref:`crate-admin-ui:index` in your browser. In the URL
 below, please replace ``cratedb.example.org`` with the host name or IP address
@@ -62,7 +62,7 @@ account::
 
 You should see something like this:
 
-.. image:: _assets/img/first-use/admin-ui.png
+.. image:: /_assets/img/getting-started/first-use/admin-ui.png
 
 
 After creating the user and granting all privileges, you should be able to

diff --git a/docs/getting-started/first-use.rst b/docs/getting-started/first-use.rst
@@ -35,7 +35,7 @@ CrateDB is running on.
 
 You should see something like this:
 
-.. image:: _assets/img/first-use/admin-ui.png
+.. image:: /_assets/img/getting-started/first-use/admin-ui.png
 
 
 .. _use-crash:

diff --git a/docs/getting-started/generate-time-series/cli.rst b/docs/getting-started/generate-time-series/cli.rst
@@ -168,7 +168,7 @@ load averages.
 In the :ref:`crate-admin-ui:index`, you should see the new table when you navigate
 to the *Tables* screen using the left-hand navigation menu:
 
-.. image:: ../_assets/img/generate-time-series/table.png
+.. image:: /_assets/img/getting-started/generate-time-series/table.png
 
 
 Record the ISS position
@@ -269,14 +269,14 @@ Run it from the command line, like so:
 
 As this runs, you should see the table filling up in the CrateDB Admin UI:
 
-.. image:: ../_assets/img/generate-time-series/rows.png
+.. image:: /_assets/img/getting-started/generate-time-series/rows.png
 
 Lots of freshly generated time series data, ready for use.
 
 And, for bonus points, if you select the arrow next to the location data, it
 will open up a map view showing the current position of the ISS:
 
-.. image:: ../_assets/img/generate-time-series/map.png
+.. image:: /_assets/img/getting-started/generate-time-series/map.png
 
 .. TIP::
 

diff --git a/docs/getting-started/generate-time-series/go.rst b/docs/getting-started/generate-time-series/go.rst
@@ -268,7 +268,7 @@ containing the `pgx`_ package and add it to ``go.mod``.
 In the :ref:`crate-admin-ui:index`, you should see the new table when you navigate
 to the *Tables* screen using the left-hand navigation menu:
 
-.. image:: ../_assets/img/generate-time-series/table.png
+.. image:: /_assets/img/getting-started/generate-time-series/table.png
 
 
 Record the ISS position
@@ -401,14 +401,14 @@ Run the script from the command line:
 As the script runs, you should see the table filling up in the
 :ref:`crate-admin-ui:index`.
 
-.. image:: ../_assets/img/generate-time-series/rows.png
+.. image:: /_assets/img/getting-started/generate-time-series/rows.png
 
 Lots of freshly generated time series data, ready for use.
 
 And, for bonus points, if you select the arrow next to the location data, it
 will open up a map view showing the current position of the ISS:
 
-.. image:: ../_assets/img/generate-time-series/map.png
+.. image:: /_assets/img/getting-started/generate-time-series/map.png
 
 .. TIP::
 

diff --git a/docs/getting-started/generate-time-series/node.rst b/docs/getting-started/generate-time-series/node.rst
@@ -171,7 +171,7 @@ Success!
 In the :ref:`crate-admin-ui:index`, you should see the new table when you navigate to
 the *Tables* screen using the left-hand navigation menu:
 
-.. image:: ../_assets/img/generate-time-series/table.png
+.. image:: /_assets/img/getting-started/generate-time-series/table.png
 
 
 Record the ISS position
@@ -323,14 +323,14 @@ Run the script from the command line:
 As the script runs, you should see the table filling up in the CrateDB Admin
 UI:
 
-.. image:: ../_assets/img/generate-time-series/rows.png
+.. image:: /_assets/img/getting-started/generate-time-series/rows.png
 
 Lots of freshly generated time series data, ready for use.
 
 And, for bonus points, if you select the arrow next to the location data, it
 will open up a map view showing the current position of the ISS:
 
-.. image:: ../_assets/img/generate-time-series/map.png
+.. image:: /_assets/img/getting-started/generate-time-series/map.png
 
 .. TIP::
 

diff --git a/docs/getting-started/generate-time-series/python.rst b/docs/getting-started/generate-time-series/python.rst
@@ -122,7 +122,7 @@ ISS position coordinates.
 In the :ref:`crate-admin-ui:index`, you should see the new table when you navigate to
 the *Tables* screen using the left-hand navigation menu:
 
-.. image:: ../_assets/img/generate-time-series/table.png
+.. image:: /_assets/img/getting-started/generate-time-series/table.png
 
 
 Record the ISS position
@@ -222,14 +222,14 @@ Run the script from the command line, like so:
 As the script runs, you should see the table filling up in the CrateDB Admin
 UI:
 
-.. image:: ../_assets/img/generate-time-series/rows.png
+.. image:: /_assets/img/getting-started/generate-time-series/rows.png
 
 Lots of freshly generated time series data, ready for use.
 
 And, for bonus points, if you select the arrow next to the location data, it
 will open up a map view showing the current position of the ISS:
 
-.. image:: ../_assets/img/generate-time-series/map.png
+.. image:: /_assets/img/getting-started/generate-time-series/map.png
 
 .. TIP::
 

diff --git a/docs/getting-started/normalize-intervals.rst b/docs/getting-started/normalize-intervals.rst
@@ -6,8 +6,8 @@ Normalize time series data intervals
 
 .. sidebar:: The ISS Orbit
 
-    .. image:: _assets/img/normalize-intervals/orbit.gif
-        :alt: An animated visualization of the ISS orbit
+    .. image:: /_assets/img/getting-started/normalize-intervals/orbit.png
+        :alt: A visualization of the ISS orbit
         :target: https://en.wikipedia.org/wiki/International_Space_Station#Orbit
 
     The ISS travels at 27,724 kilometers per hour and orbits Earth
@@ -122,7 +122,7 @@ the top right-hand corner), then *Notebook* → *Python 3*.
 Type your Python code at the input prompt. Then, select *Run* (Shift-Enter ⇧⏎)
 to evaluate the code:
 
-.. image:: _assets/img/normalize-intervals/jupyter-hello-world.png
+.. image:: /_assets/img/getting-started/normalize-intervals/jupyter-hello-world.png
 
 You can re-evaluate input blocks as many times as you like.
 
@@ -367,7 +367,7 @@ You can test the ``plot()`` function by passing in the return value of
 
 Jupyter should display a plot like this:
 
-.. image:: _assets/img/normalize-intervals/raw-data.png
+.. image:: /_assets/img/getting-started/normalize-intervals/raw-data.png
 
 Above, notice that:
 
@@ -490,7 +490,7 @@ You can plot this data like before:
 
     plot(data_by_minute())
 
-.. image:: _assets/img/normalize-intervals/data-by-minute.png
+.. image:: /_assets/img/getting-started/normalize-intervals/data-by-minute.png
 
 Here, notice that the individual data points are now visible (i.e., the
 apparent line in the previous diagram is now discernible as a series of
@@ -662,7 +662,7 @@ Plot the data:
 
     plot(null_by_minute_24h())
 
-.. image:: _assets/img/normalize-intervals/null-by-minute-24h.png
+.. image:: /_assets/img/getting-started/normalize-intervals/null-by-minute-24h.png
 
 This plot displays null values for a full 24 hour period.
 
@@ -748,11 +748,11 @@ Plot the data:
 
     plot(data_24h())
 
-.. image:: _assets/img/normalize-intervals/data-24h.png
+.. image:: /_assets/img/getting-started/normalize-intervals/data-24h.png
 
 And here's what it looks like if you wait a few more hours:
 
-.. image:: _assets/img/normalize-intervals/data-24h-more.png
+.. image:: /_assets/img/getting-started/normalize-intervals/data-24h-more.png
 
 The finished result is a visualization that uses time series normalization and
 resamples raw data to regular intervals with the interpolation of missing values.

diff --git a/docs/integrations/azure-functions.rst b/docs/integrations/azure-functions.rst
@@ -21,7 +21,7 @@ new data flowing into an IoT Hub.
 
 .. _figure_1:
 
-.. figure:: azfunc.png
+.. figure:: /_assets/img/integrations/azfunc.png
    :align: center
 
 An Azure Function is a short-lived, serverless computation that is triggered

diff --git a/docs/integrations/kafka-connect.rst b/docs/integrations/kafka-connect.rst
@@ -38,7 +38,7 @@ This results in the following architecture:
 
 .. _figure_1:
 
-.. figure:: kafka-connect.png
+.. figure:: /_assets/img/integrations/kafka-connect.png
    :align: center
 
 

diff --git a/docs/integrations/ml-dist.rst b/docs/integrations/ml-dist.rst
@@ -332,7 +332,7 @@ successive epochs by stopping training, using the ``EarlyStopping`` callback.
     plt.plot(hist.history["loss"])
     plt.show()
 
-.. figure:: mlp_model_train_loss.png
+.. figure:: /_assets/img/integrations/mlp_model_train_loss.png
    :align: left
 
 This figure shows us the loss of each epoch. In the first 200 epochs it is

diff --git a/docs/integrations/powerbi-desktop.rst b/docs/integrations/powerbi-desktop.rst
@@ -100,13 +100,13 @@ Creating a DSN for CrateDB
 First, verify that you have installed the PostgreSQL ODBC driver by searching
 for and opening the ODBC Data Sources application for your architecture:
 
-.. figure:: powerbi-start-menu.png
+.. figure:: /_assets/img/integrations/powerbi-start-menu.png
    :align: center
 
 Navigate to the drivers tab, where you should see the PostgreSQL ODBC drivers
 you have installed:
 
-.. figure:: powerbi-postgres-drivers.png
+.. figure:: /_assets/img/integrations/powerbi-postgres-drivers.png
    :align: center
 
 If this is correct, you can add a User DSN by navigating to the User DSN tab
@@ -119,7 +119,7 @@ are using a 64-bit Windows. Otherwise, select *PostgreSQL Unicode(x32)*.
    <cratedb-powerbi-service>` integration document, then you should create
    this DSN as a **System DSN**, not a **User DSN**.
 
-.. figure:: powerbi-driver-select.png
+.. figure:: /_assets/img/integrations/powerbi-driver-select.png
    :align: center
 
 Set up the data source with the following parameters:
@@ -140,7 +140,7 @@ If your CrateDB instance uses SSL, enable the SSL mode. If the CrateDB user
 you're connecting with is password protected, add its password to the Password
 field.
 
-.. figure:: powerbi-dsn-setup.png
+.. figure:: /_assets/img/integrations/powerbi-dsn-setup.png
    :align: center
 
 You can click *Test* to verify that the DSN is configured correctly. Once this
@@ -153,18 +153,18 @@ Connecting Power BI to CrateDB
 Once you have created the DSN, open up Power BI and click *Get Data* from the
 menu ribbon. Select *ODBC* from the list of available data sources:
 
-.. figure:: powerbi-source.png
+.. figure:: /_assets/img/integrations/powerbi-source.png
    :align: center
 
 Select CrateDB from the DSN list and click *OK*:
 
-.. figure:: powerbi-crate-dsn.png
+.. figure:: /_assets/img/integrations/powerbi-crate-dsn.png
    :align: center
 
 Within the ``doc`` schema, you should see and be able to add the
 ``population_data`` table:
 
-.. figure:: powerbi-table-navigator.png
+.. figure:: /_assets/img/integrations/powerbi-table-navigator.png
    :align: center
 
 From here you can transform the data as you wish, or click *Load* to load
@@ -184,7 +184,7 @@ panel into the *Legend* section of the visualizations tab.
 
 The pie chart will be updated automatically, and will produce the following:
 
-.. figure:: powerbi-pie-chart.png
+.. figure:: /_assets/img/integrations/powerbi-pie-chart.png
    :align: center
 
 

diff --git a/docs/integrations/powerbi-gateway.rst b/docs/integrations/powerbi-gateway.rst
@@ -52,7 +52,7 @@ Follow Microsoft's documentation on how to `install`_ and `configure`_ the
 on-premises gateway. When it is finished installing and configuring, you
 should see something like the following status:
 
-.. figure:: powerbi-gateway-status.png
+.. figure:: /_assets/img/integrations/powerbi-gateway-status.png
    :align: center
 
 Ensure that the **Power BI** status for the gateway is **Ready**.
@@ -68,7 +68,7 @@ guide to do this.
 
 After running through that guide, we should have the following report:
 
-.. figure:: powerbi-pie-chart.png
+.. figure:: /_assets/img/integrations/powerbi-pie-chart.png
    :align: center
 
 
@@ -79,16 +79,16 @@ With your report created on Power BI desktop, you can now publish it to the
 online Power BI service. First, click the *Publish* button in the ribbon. Next,
 choose a destination to publish to:
 
-.. figure:: powerbi-publish-destination.png
+.. figure:: /_assets/img/integrations/powerbi-publish-destination.png
    :align: center
 
 When your publishing is successful, you can then open the report in the
 Power BI service:
 
-.. figure:: powerbi-publish-success.png
+.. figure:: /_assets/img/integrations/powerbi-publish-success.png
    :align: center
 
-.. figure:: powerbi-published-report.png
+.. figure:: /_assets/img/integrations/powerbi-published-report.png
    :align: center
 
 The report can now be shared via its URL. However, this is just a static
@@ -107,13 +107,13 @@ Configuring The Gateway
 
 Within the Power BI service's settings, select *Manage Gateways*:
 
-.. figure:: powerbi-manage-gateways.png
+.. figure:: /_assets/img/integrations/powerbi-manage-gateways.png
    :align: center
 
 You should see the gateway cluster you set up. When you click *Test all
 connections*, you should see your cluster has the 'Online' status:
 
-.. figure:: powerbi-gateway-clusters.png
+.. figure:: /_assets/img/integrations/powerbi-gateway-clusters.png
    :align: center
 
 Click *Add data sources to use the gateway*. In the data source settings,
@@ -130,7 +130,7 @@ the DSN when connecting Power BI Desktop to CrateDB. In this case, it was
 Hit apply, and if the settings are correct it will display that the connection
 was successful:
 
-.. figure:: powerbi-connection-successful.png
+.. figure:: /_assets/img/integrations/powerbi-connection-successful.png
    :align: center
 
 Once successful, go to the *Users* tab and select the users you would like to
@@ -139,13 +139,13 @@ be able to access this data source to publish reports.
 Now, navigate back to the Power BI Service and click on the extra options
 for your ``population report`` data set, and click *Schedule refresh*.
 
-.. figure:: powerbi-schedule-refresh.png
+.. figure:: /_assets/img/integrations/powerbi-schedule-refresh.png
    :align: center
 
 In the *Gateway connection* section of the dataset's settings, configure
 the dataset to use the data gateway you set up previously and click apply:
 
-.. figure:: powerbi-gateway-connection.png
+.. figure:: /_assets/img/integrations/powerbi-gateway-connection.png
    :align: center
 
 The report is now configured to use the gateway.
@@ -172,20 +172,20 @@ Now that the dataset powering our report has changed, you can refresh it. As
 before, click on the extra settings for the ``population report`` dataset, and
 click *Refresh now*.
 
-.. figure:: powerbi-refresh-now.png
+.. figure:: /_assets/img/integrations/powerbi-refresh-now.png
    :align: center
 
 If you navigate to the dataset settings, you should see that a refresh is in
 progress:
 
-.. figure:: powerbi-refresh-in-progress.png
+.. figure:: /_assets/img/integrations/powerbi-refresh-in-progress.png
    :align: center
 
 Once it succeeds, you should see a message in its place about when the
 successful refresh occurred. Once done, you can navigate back to your report
 and refresh it to see the new dataset underlying the pie chart:
 
-.. figure:: powerbi-refreshed-report.png
+.. figure:: /_assets/img/integrations/powerbi-refreshed-report.png
    :align: center
 
 As you can see, the report no longer contains 'Europe' as one of the regions.

diff --git a/docs/integrations/r.rst b/docs/integrations/r.rst
@@ -179,7 +179,7 @@ of these properties across each species.
     > boxplot(petal_length~species, data=iris_dataset, main="Petal Length by Species")
     > boxplot(petal_width~species, data=iris_dataset, main="Petal Width by Species")
 
-.. figure:: r-iris-features.png
+.. figure:: /_assets/img/integrations/r-iris-features.png
    :align: center
 
 As we can see, the lengths and widths of sepals and petals are very good