DJ Lobster

Thanks so much for the thorough reply! I had the file structure down correctly. I'm still kind of new to Docker so I took your suggestion and just waited after it stopped to see what happened, but it was actually stopped and never came back up. Once I found out how, I confirmed by using 'docker ps -a' to see the status of it. I still have no idea why it was doing that and nothing at all was being logged from what I could tell, the logs just stop suddenly. I didn't change anything, but the latest update fixed my issues. I'm scanning everything fine now and I haven't had any issues besides a database issue that I was able to resolve easily. I'm able to restart/stop and start the container now without issues with the latest fix as well! I think this is exactly what I've been looking for and am excited about the upcoming features and some of the ideas I've seen in the discussions/issues on the GitHub. I'll be donating later this week for sure!

Have you been able to get this working consistently? The Twitch integration works fine, token fetched. I get Romm working to the point where it's scanning the library and then it identifies my snes folder as the right console, but then finds nothing (already set up the folder structure exactly like the wiki says) or while searching the container just stops. Once it stops once, it won't start again unless I edit the template like you are. I've deleted everything and tried again 3 times in the last week in case I was doing something wrong that I missed. I'm not getting any useful logs, all it says is: INFO: [RomM][2023-12-28 10:59:40] Starting scheduler INFO: [RomM][2023-12-28 10:59:40] Watching /romm/library/roms for changes I've also tried using the experimental redis options, setting up auth, just to see if I get a different outcome but it's always the same.

I like this a lot. I was just setting up the plugin for the first time and was coming here to request this feature. Looking forward to the update!