RomM App For Cloudron

[eyecreate]

I updated the metadata to support the community app format. Tested on the server you linked.

Install URL: https://git.cloudron.io/eyecreate/romm/-/raw/main/CloudronVersions.json

[murgero]

@eyecreate amazing! I'll be installing this I think

[humpty]

do you HAVE to add metadata provider for it to work? I uploaded some NES games, ran a scan, restarted the app, and yet nothing shows in the library. Can't I use this in "offline" mode? As in no calls to third parties?

Edit: created a screenscraper account, added the user/pass to the env.sh, and restarted the app. Some dev api error is showing up. I couldn't find a way to create a dev api anywhere on their site.

[eyecreate]

There is no metadata by default, so yes, it has to reach out somewhere unless you want to type out your own metadata into the editor. It should by default have hasheous, but I haven't always had tons of success with it's proxy.
Sorry about the dev api error. screenscraper isn't usable right now without me applying for a dev key.(screenscraper needs a dev key and user auth) Romm used to ship their key in the code, but removed it recently.
On my own server, I've set up IGDB for now.

[humpty]

@eyecreate said:

I've set up IGDB for now.

I'll give that a shot. Thank you.

[humpty]

@eyecreate I started over and added the IGDB info and restarted the app then proceeded with the initial account creation. IGDB's connection is valid. I uploaded a new set of NES roms that I got from Vimmdotnet (in case it was a rom issue). Ran a scan and I still don't see them. They are being detected though. What am I doing wrong?

Edit: I downloaded the NES roms from the romM demo site to make sure it's not a rom issue so it must be a scan issue. I keep getting this error when manually triggering one regardless of which method I try (quick, complete, etc) Scan failed: Quick Scan is already queued

[humpty]

Started over again. This time I uploaded the roms and set IGDB info before setting up the account/app. I triggered a quick scan and in another tab I watched the log. The scan is definitely getting stuck. I triggered a new scan attempt in another tab and you can see the failed messages.

[humpty]

On RomM's discord, I found some clues related to quick scan getting stuck:

Clue 1

reverse proxy setup that enable Web sockets is on

Clue 2

This is for proxmox but might be related?

`There is a new worker just for scans and the update script doesn't create the new service, or seem to update the ones that are there. The updates are in the script to make a new romm lxc though.`
https://github.com/community-scripts/ProxmoxVE/blob/main/install/romm-install.sh (starts at line 353)

Clue 3

disable launchbox

If it's a typo and they meant lunchbox, I can definitely help with that.

Another user reported having scan issues in 5.3.1, but not in 5.2.0. I joined late to the party so I don't have a 5.2.0 backup to revert to to confirm.

[eyecreate]

There were some changes to library structure recently, but I didnt think they changed anything related to the workers to affect scanning. I'll take a closer look and see if I missed a change related to scanning.

[eyecreate]

I looked more at the code and it seems the workers need to specifically be marked to scan now or else they don't get scan tasks. I'll update that in the image.

[eyecreate]

Romm should be updated now to fix not having any scanning happen.

[humpty]

Success! It's scanning as I'm typing this!

THANK YOU!

[humpty]

Vice city, Robocop, Blades of Steel... Man, the memories 🥹