[Bug] Database Erasing Bug

[truevox]

RomM version
3.5.0

Describe the bug
After creating a roms folder at the same level as my game system folder and uploading a ROM through the web interface, ROMM stopped recognizing ROMs that aren’t stored in the new roms/gamesystem path. A rescan partially restored the ROMs, but save states and other associated data seem to still be missing.

To Reproduce
Steps to reproduce the behavior:

1. Set up your library with this structure: /home/user/library/gamesystem/roms/game.
2. Create a new roms folder in the same directory as the game system folder.
3. Upload a ROM through the ROMM web interface.
4. Perform a quick scan in ROMM.
5. Notice that ROMM no longer recognizes ROMs outside of roms/gamesystem.

Expected behavior
ROMM should continue detecting ROMs in the original folder structure. After creating the new folder and uploading a ROM, ROMM prioritized the roms/gamesystem structure, causing ROMs outside of that structure to disappear until a rescan was performed.

Desktop (please complete the following information):

• OS: Docker container under Ubuntu 24 LTS
• Browser: ChromeOS
• Version: 127

Additional context
According to a discussion on Discord, ROMM seems to prefer the structure /library/roms/gamesystem/game but will work with /library/gamesystem/roms/game. A quick scan restored the ROMs, but save states and other data still appear to be missing. It was suggested that an environment variable could be added to explicitly set which folder structure ROMM should prioritize.