New diagrams with mysql

Author: benitav

architecture/architecture-overview.mdx

@@ -4,7 +4,7 @@ description: The core components of PowerSync are the service and client SDKs
 ---
 
 <Frame>
-  <img src="/images/powersync-docs-diagram-architecture-overview.png"/>
+  <img src="/images/architecture/powersync-docs-diagram-architecture-overview.png"/>
 </Frame>
 
 The [PowerSync Service](/architecture/powersync-service) and client SDK operate in unison to keep client-side SQLite databases in sync with a backend database. Learn about their architecture:

images/architecture-1.avif

@@ -7,7 +7,7 @@ sidebarTitle: Overview
 
 The typical components of a self-hosted production environment are:
 <Frame caption="Self-hosted PowerSync architecture">
-  <img src="/images/powersync-architecture-diagram-self-host (1).png"/>
+  <img src="/images/self-hosting/powersync-architecture-diagram-self-host.png"/>
 </Frame>
 
 The self-hosted deployment is run via Docker. A Docker image is distributed via [Docker Hub](https://hub.docker.com/r/journeyapps/powersync-service). Run PowerSync using:

images/architecture/powersync-docs-diagram-architecture-overview.png

@@ -11,7 +11,7 @@ mode: wide
 Below is an architecture diagram of a successful deployment:
 
 <Frame caption="PowerSync Deployment Architecture">
-  <img src="/images/self-hosting-2.avif"/>
+  <img src="/images/self-hosting/powersync-architecture-diagram-self-host.png"/>
 </Frame>
 
 Data doesn't always flow in the direction of your firewall rules, so the below table documents which components are making connections to others: