Skip to content

Commit eaa2ed8

Browse files
authored
Merge branch 'rommapp:main' into main
2 parents d87636a + 4f48bcb commit eaa2ed8

7 files changed

Lines changed: 570 additions & 456 deletions

File tree

docs/Getting-Started/Environment-Variables.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -70,6 +70,8 @@ This is a complete list of available environment variables; required variables a
7070
| LAUNCHBOX_API_ENABLED | Enable LaunchBox API integration | | `false` |
7171
| PLAYMATCH_API_ENABLED | Enable PlayMatch API integration | | `false` |
7272
| HASHEOUS_API_ENABLED | Enable Hasheous API integration | | `false` |
73+
| FLASHPOINT_API_ENABLED | Enable Flashpoint API integration | | `false` |
74+
| HLTB_API_ENABLED | Enable HowLongToBeat API integration | | `false` |
7375

7476
## Authentication
7577

Lines changed: 93 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,93 @@
1+
<!-- trunk-ignore-all(markdownlint/MD041) -->
2+
3+
## Migrating RomM to a new system
4+
5+
Migrating RomM to a new system is possible, but all of the docker volumes must be copied for RomM to run correctly.
6+
7+
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
8+
9+
RomM should be stopped before following this guide.
10+
11+
```yaml
12+
volumes:
13+
mysql_data:
14+
romm_resources:
15+
romm_redis_data:
16+
17+
services:
18+
romm:
19+
volumes:
20+
- romm_resources
21+
- romm_redis_data
22+
romm-db:
23+
volumes:
24+
- mysql_data
25+
```
26+
27+
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.
28+
29+
### Determining the docker root directory and copying the volumes
30+
31+
1. First determine the docker root directory
32+
33+
```bash
34+
docker info | grep 'Docker Root Dir'
35+
```
36+
37+
The expected output on a standard linux system:
38+
39+
```bash
40+
Docker Root Dir: /var/lib/docker
41+
```
42+
43+
2. Double check that the volumes have been created by docker and are owned by the docker engine
44+
45+
```bash
46+
docker volume ls
47+
```
48+
49+
Following the default quick start guide the following volumes will have been made
50+
51+
```bash
52+
DRIVER VOLUME NAME
53+
local romm_mysql_data
54+
local romm_romm_redis_data
55+
local romm_romm_resources
56+
```
57+
58+
3. Inspect each volume to get the exact location of the volume data
59+
60+
```bash
61+
docker volume inspect romm_mysql_data | grep Mountpoint
62+
```
63+
64+
- The output of the `docker inspect` will return the exact storage location of the volumes data
65+
66+
```bash
67+
"Mountpoint": "/var/lib/docker/volumes/romm_mysql_data/_data",
68+
```
69+
70+
4. Copy those volumes into a new location so that they can be safely migrated to a new system **each volume needs to be in its own folder**
71+
72+
```bash
73+
cp -r /var/lib/docker/volumes/romm_mysql_data/_data/ /your/new/path/romm_mysql_data
74+
75+
cp -r /var/lib/docker/volumes/romm_romm_redis_data/_data /your/new/path/romm_romm_redis_data
76+
77+
cp -r /var/lib/docker/volumes/romm_romm_resources/_data /your/new/path/romm_romm_resources
78+
```
79+
80+
5. Update the `docker-compose.yml` volume paths with the newly copied data to determine RomM still loads correctly.
81+
82+
```yaml
83+
services:
84+
romm:
85+
volumes:
86+
- /your/new/path/romm_romm_resources # romm_resources
87+
- /your/new/path/romm_romm_redis_data # romm_redis_data
88+
romm-db:
89+
volumes:
90+
- /your/new/path/romm_mysql_data # mysql_data
91+
```
92+
93+
If RomM starts up correctly, then it is safe to copy all of your RomM folders to a new system.

docs/Platforms-and-Players/Supported-Platforms.md

Lines changed: 467 additions & 455 deletions
Large diffs are not rendered by default.

docs/Usage/LibraryManagement.md

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@ In all views, a grid icon is present in the upper right of the screen or contain
1515

1616
Platform cards can be clicked to go directly to the platform. A game card can be interacted in a few ways: putting your mouse over it allows you to download the game, play the game if the system is supported, or open a context menu giving you the option to manually match game information using a metadata agent, edit existing data, refresh the metadata, and add or remove the game from favourites or collections.
1717

18+
![game card](https://raw.githubusercontent.com/rommapp/docs/refs/heads/main/docs/resources/usage/gameCard.png)
19+
![context menu](https://raw.githubusercontent.com/rommapp/docs/refs/heads/main/docs/resources/usage/ContextMenu.png)
20+
1821
Clicking a platform will take you to the platform view, while clicking a game will take you to the game view.
1922

2023
### Filters
@@ -39,7 +42,7 @@ The filters that can be toggled include:
3942
Next there is a platform drop down. This allows you to select a platform you want to restrict your view to showing.
4043

4144
After this you can filter by metadata: Game Genre, Franchise, Collections, Company, Age Rating, Region, and Language.
42-
One additional filter exists after these: Status. This allows you to use the "personal" data tab on any game to track your progress of the game (Never Playing, Backlogged, Compete, etc).
45+
One additional filter exists after these: Status. This allows you to use the "personal" data tab on any game to track your progress of the game (never playing, backlogged, complete, etc).
4346

4447
## The Menu bar
4548

@@ -49,6 +52,8 @@ The menu bar is designed for quick access to the tools of your RomM server.
4952

5053
Simply typing text into the search bar will bring up game cards for each game that matches the query. To the left of the search bar are two icons: the view filters and the new collection button.
5154

55+
![search bar](https://raw.githubusercontent.com/rommapp/docs/refs/heads/main/docs/resources/usage/SearchBar.png)
56+
5257
### List Platforms
5358

5459
The Platforms button opens a drawer listing all of the known platforms in RomM. Clicking on any of these will create a search that is limited to that platform.
@@ -112,6 +117,8 @@ Following that are the platform settings, which consists of the style of cover u
112117

113118
Finally, in the Danger Zone, is a Delete Platform button. This removes the platform from the database, it does NOT touch the files on your system. If you delete a platform in this way, scanning for new platforms will restore it, and all games will have to have their metadata re-matched.
114119

120+
![platform drawer](https://raw.githubusercontent.com/rommapp/docs/refs/heads/main/docs/resources/usage/PlatformView.png)
121+
115122
### Firmware
116123

117124
Next to the platform drawer button is the firmware button. This allows you to review all of the firmware for that system, and upload firmware using the user interface.
6.89 KB
Loading
158 Bytes
Loading
22.9 KB
Loading

0 commit comments

Comments
 (0)