run trunk fmt

docs/Maintenance/Migrating-to-new-machine.md

@@ -1,6 +1,8 @@
-# Migrating RomM to a new system
+<!-- trunk-ignore-all(markdownlint/MD041) -->
 
-Migrating RomM to a new system is possible; all of the docker volumes must be copied for RomM to run correctly.
+## Migrating RomM to a new system
+
+Migrating RomM to a new system is possible, but all of the docker volumes must be copied for RomM to run correctly.
 
 Following the the setup in the [Quick Start Guide](https://docs.romm.app/latest/Getting-Started/Quick-Start-Guide/#build) these volumes are created be default
 
@@ -15,21 +17,25 @@ volumes:
 services:
     romm:
         volumes:
-         - romm_resources
-         - romm_redis_data
+            - romm_resources
+            - romm_redis_data
     romm-db:
         volumes:
-         - mysql_data
+            - mysql_data
 ```
 
 These volumes will need to manually moved to the new system. This is a straightforward process that includes determining their location and then copying them.
 
 ### Determining the docker root directory and copying the volumes
+
 1. First determine the docker root directory
+
 ```bash
 docker info | grep 'Docker Root Dir'
 ```
+
 The expected output on a standard linux system:
+
 ```bash
 Docker Root Dir: /var/lib/docker
 ```
@@ -42,7 +48,7 @@ docker volume ls
 
 Following the default quick start guide the following volumes will have been made
 
-```
+```bash
 DRIVER    VOLUME NAME
 local     romm_mysql_data
 local     romm_romm_redis_data
@@ -55,7 +61,8 @@ local     romm_romm_resources
 docker volume inspect romm_mysql_data | grep Mountpoint
 ```
 
-* The output of the ``docker inspect`` will return the exact storage location of the volumes data
+- The output of the `docker inspect` will return the exact storage location of the volumes data
+
 ```bash
 "Mountpoint": "/var/lib/docker/volumes/romm_mysql_data/_data",
 ```
@@ -65,26 +72,22 @@ docker volume inspect romm_mysql_data | grep Mountpoint
 ```bash
 cp -r /var/lib/docker/volumes/romm_mysql_data/_data/ /your/new/path/romm_mysql_data
 
-cp-r /var/lib/docker/volumes/romm_romm_redis_data/_data /your/new/path/romm_romm_redis_data
+cp -r /var/lib/docker/volumes/romm_romm_redis_data/_data /your/new/path/romm_romm_redis_data
 
 cp -r /var/lib/docker/volumes/romm_romm_resources/_data /your/new/path/romm_romm_resources
 ```
 
-5. Update the ``docker-compose.yml`` volume paths with the newly copied data to determine RomM still loads correctly.
+5. Update the `docker-compose.yml` volume paths with the newly copied data to determine RomM still loads correctly.
 
 ```yaml
 services:
     romm:
         volumes:
-#         - romm_resources
-         - /your/new/path/romm_romm_resources
-#         - romm_redis_data
-         - /your/new/path/romm_romm_redis_data
+            - /your/new/path/romm_romm_resources # romm_resources
+            - /your/new/path/romm_romm_redis_data # romm_redis_data
     romm-db:
         volumes:
-#         - mysql_data
-        - /your/new/path/romm_mysql_data
+            - /your/new/path/romm_mysql_data # mysql_data
 ```
 
-
-If RomM starts up correctly, then it is safe to copy all of your RomM folders to a new system.
+If RomM starts up correctly, then it is safe to copy all of your RomM folders to a new system.