Documentation edits made through Mintlify web editor

Author: mintlify[bot]

installation/database-setup.mdx

@@ -37,37 +37,34 @@ We have documented steps for some hosting providers:
 
     <PostgresPowerSyncPublication />
   </Accordion>
-
   <Accordion title="AWS RDS">
     ### Prerequisites
 
     The instance must be publicly accessible using an IPv4 address.
 
     <Frame>
-      <img src="/images/setup-1.avif" />
+      ![](/images/setup-1.avif)
     </Frame>
-
     Access may be restricted to specific IPs if required — see [IP Filtering](/installation/database-setup/security-and-ip-filtering).
 
     ### 1. Enable logical replication
 
     Set the `rds.logical_replication` parameter to `1` in the parameter group for the instance:
 
     <Frame>
-      <img src="/images/setup-2.png" />
+      ![](/images/setup-2.png)
     </Frame>
-
     ### 2. Create a PowerSync database user
 
     Create a PowerSync user on Postgres:
 
     ```sql
     -- SQL to create powersync user
     CREATE ROLE powersync_role WITH BYPASSRLS LOGIN PASSWORD 'myhighlyrandompassword';
-
+    
     -- Allow the role to perform replication tasks
     GRANT rds_replication TO powersync_role;
-
+    
     -- Set up permissions for the newly created role
     -- Read-only (SELECT) access is required
     GRANT SELECT ON ALL TABLES IN SCHEMA public TO powersync_role;
@@ -79,7 +76,6 @@ We have documented steps for some hosting providers:
 
     <PostgresPowerSyncPublication />
   </Accordion>
-
   <Accordion title="Azure Postgres">
     PowerSync supports both "Azure Database for PostgreSQL" and "Azure Database for PostgreSQL Flexible Server".
 
@@ -99,16 +95,14 @@ We have documented steps for some hosting providers:
 
     <PostgresPowerSyncPublication />
   </Accordion>
-
   <Accordion title="Google Cloud SQL">
     ### 1. Enable logical replication
 
     In Google Cloud SQL Postgres, enabling the logical replication is done using flags:
 
     <Frame>
-      <img src="/images/setup-3.png" />
+      ![](/images/setup-3.png)
     </Frame>
-
     ### 2. Create a PowerSync database user
 
     <PostgresPowerSyncUser />
@@ -117,13 +111,13 @@ We have documented steps for some hosting providers:
 
     <PostgresPowerSyncPublication />
   </Accordion>
-
   <Accordion title="Neon">
     Neon is a serverless Postgres environment with an innovative pricing model that separates storage and compute.
 
     ### 1. Enable Logical Replication
 
-    To [enable logical replication](https://neon.tech/docs/guides/logical-replication-postgres#prepare-your-source-neon-database): 
+    To [enable logical replication](https://neon.tech/docs/guides/logical-replication-postgres#prepare-your-source-neon-database):
+
     1. Select your project in the Neon Console.
     2. On the Neon Dashboard, select **Settings**.
     3. Select **Logical Replication**.
@@ -137,7 +131,6 @@ We have documented steps for some hosting providers:
 
     <PostgresPowerSyncPublication />
   </Accordion>
-
   <Accordion title="Fly Postgres">
     Fly Postgres is a [Fly](https://fly.io/) app with [flyctl](https://fly.io/docs/flyctl/) sugar on top to help you bootstrap and manage a database cluster for your apps.
 
@@ -150,9 +143,8 @@ We have documented steps for some hosting providers:
     ```
 
     <Frame>
-      <img src="/images/setup-5.avif" />
+      ![](/images/setup-5.avif)
     </Frame>
-
     ### 2. Create a PowerSync database user
 
     <PostgresPowerSyncUser />
@@ -175,18 +167,17 @@ For other providers and self-hosted databases:
   If you are managing Postgres yourself, set `wal_level = logical` in your config file:
 
   <Frame>
-    <img src="/images/setup-6.avif" />
+    ![](/images/setup-6.avif)
   </Frame>
-
   Alternatively, you can use the below SQL commands to check and enable logical replication:
 
   ```sql
   -- Check the replication type
-
+  
   SHOW wal_level;
-
+  
   -- Enable logical replication
-
+  
   ALTER SYSTEM SET wal_level = logical;
   ```
 
@@ -215,7 +206,7 @@ Due to the logical replication requirement, not all Postgres hosting providers a
 
 ### Permissions required - MongoDB Atlas
 
-For MongoDB Atlas databases, the minimum permissions are:
+For MongoDB Atlas databases, the minimum permissions when using built-in roles are:
 
 ```
 readWrite@<your_database>._powersync_checkpoints
@@ -240,15 +231,14 @@ readAnyDatabase@admin
 
 For self-hosted MongoDB, or for creating custom roles on MongoDB Atlas, PowerSync requires the following privileges/granted actions:
 
-* On the database being replicated: `listCollections`
-* On all collections in the database: `changeStream`
-   * This must apply to the entire database, not individual collections. Specify `collection: ""`
-   * If replicating from multiple databases, this must apply to the entire cluster. Specify `db: ""`
-* On each collection being replicated: `find`
-* On the `_powersync_checkpoints` collection: `createCollection`, `dropCollection`, `find`, `changeStream`, `insert`, `update`, and `remove`
-* To allow PowerSync to automatically enable [`changeStreamPreAndPostImages`](#post-images) on
-replicated collections, additionally add the `collMod` permission on all replicated collections.
-
+- On the database being replicated: `listCollections`
+- On all collections in the database: `changeStream`
+  - This must apply to the entire database, not individual collections. Specify `collection: ""`
+  - If replicating from multiple databases, this must apply to the entire cluster. Specify `db: ""`
+- On each collection being replicated: `find`
+- On the `_powersync_checkpoints` collection: `createCollection`, `dropCollection`, `find`, `changeStream`, `insert`, `update`, and `remove`
+- To allow PowerSync to automatically enable [`changeStreamPreAndPostImages`](#post-images) on
+  replicated collections, additionally add the `collMod` permission on all replicated collections.
 
 ### Post-Images
 
@@ -258,9 +248,7 @@ This requires the `changeStreamPreAndPostImages` option to be enabled on replica
 PowerSync supports three configuration options for post-images:
 
 1. **Off**: (`post_images: off`): Uses `fullDocument: 'updateLookup'` for backwards compatibility. This was the default for older instances. However, this may lead to consistency issues, so we strongly recommend enabling post-images instead.
-
 2. **Automatic**: (`post_images: auto_configure`) The **default** for new instances: Automatically enables the `changeStreamPreAndPostImages` option on collections as needed. Requires the permissions/privileges mentioned above. If a collection is removed from [Sync Rules](/usage/sync-rules), developers can manually disable `changeStreamPreAndPostImages`.
-
 3. **Read-only**: (`post_images: read_only`): Uses `fullDocument: 'required'` and requires `changeStreamPreAndPostImages: { enabled: true }` to be set on every collection referenced in the [Sync Rules](/usage/sync-rules). Replication will error if this is not configured. This option is ideal when permissions are restricted.
 
 To manually configure collections for `read_only` mode, run this on each collection:
@@ -282,23 +270,21 @@ Post-images can be configured for PowerSync instances as follows:
 
 <CardGroup cols="2">
   <Card title="PowerSync Cloud:">
-    Configure the **Post Images** setting in the connection configuration in the Dashboard (right-click on your instance to edit it). 
+    Configure the **Post Images** setting in the connection configuration in the Dashboard (right-click on your instance to edit it).
   </Card>
   <Card title="Self-Hosted PowerSync:" href="https://github.com/powersync-ja/self-host-demo/blob/main/demos/nodejs-mongodb/config/powersync.yaml#L11" cta="See an example">
-    Configure `post_images` in the `config.yaml` file. 
+    Configure `post_images` in the `config.yaml` file.
   </Card>
 </CardGroup>
 
 ### MongoDB Atlas private endpoints using AWS PrivateLink
 
 If you need to use private endpoints with MongoDB Atlas, see [Private Endpoints](/installation/database-setup/private-endpoints) (AWS only).
 
-
 ### Migrating from MongoDB Atlas Device Sync
 
 For more information on migrating from Atlas Device Sync to PowerSync, see our [migration guide](/migration-guides/mongodb-atlas).
 
-
 ## <Icon icon="dolphin" iconType="solid" size="24" /> MySQL (Alpha)
 
 <Info>
@@ -313,11 +299,9 @@ MySQL connections use the [binary log](https://dev.mysql.com/doc/refman/8.4/en/b
 
 Generally, this requires the following config:
 
-* `gtid_mode` : `ON`
-
-* `enforce_gtid_consistency` : `ON`
-
-* `binlog_format` : `ROW`
+- `gtid_mode` : `ON`
+- `enforce_gtid_consistency` : `ON`
+- `binlog_format` : `ROW`
 
 PowerSync also requires a user with replication permissions on the database. An example:
 
@@ -346,5 +330,4 @@ Next, connect PowerSync to your database:
   <Card title="For Self-Hosted PowerSync:" href="/self-hosting/installation/powersync-service-setup#powersync-configuration">
     Refer to **PowerSync Service Setup** in the Self-Hosting section.
   </Card>
-</CardGroup>
-
+</CardGroup>