RomM App For Cloudron
-
With the help of the amazing devs @ the RomM Discord (Not linked as they have everything on their site below) I was able to port their beautiful ROM manager to Cloudron. See the below for details!
RomM App
Your beautiful, powerful, self-hosted rom manager and player.
- RomM Site
- Cloudron App Source (With install instructions until it gets published!)
- Demo Site (Demo Site only hosts public domain and / or copy-left ROMs!)
Scan, enrich, and browse your game collection with a clean and responsive interface.
With support for multiple platforms, various naming schemes and custom tags, RomM is a must-have for anyone who plays on emulators.
RomM is an All-in-one app for managing your classic / retro game collection.Screenshots:
Known Issues:
- [FIXED]
Currently due to how RomM works, I had to symlink the special library and config folders. this causes some issues in cloudron's app file-explorer but should still work fine via SSH or FTP. - [FIXED]
Looks like due to parent dockerfile conflicts, updating the app seems to wipe library data. I am working to rebuild the parent dockerfile to remove the volume tags so they can be properly moved to /app/data
-
N nebulon moved this topic from App Wishlist
-
For Cloudron App Store, the packages are generally written from scratch and don't have external deps i.e they are pinned to specific versions etc.
-
Basically on Cloudron apps should be derived from the Cloudron base image, to ensure all required tools are included. Otherwise some Cloudron features will not work correctly.
But also the app versions have to be pinned to specific releases, otherwise rebuilding a package from a tag can result in different images each time if some upstream images change.
Since you start with
mitchellurgero/romm:local-cloudron-changesmaybe you have those pinned there, but not sure where that is defined. -
Basically on Cloudron apps should be derived from the Cloudron base image, to ensure all required tools are included. Otherwise some Cloudron features will not work correctly.
But also the app versions have to be pinned to specific releases, otherwise rebuilding a package from a tag can result in different images each time if some upstream images change.
Since you start with
mitchellurgero/romm:local-cloudron-changesmaybe you have those pinned there, but not sure where that is defined.@nebulon I am working with the ROMM devs to fix a couple bugs I've found while packaging the app, however all cloudron features seem to be working as expected. Cloudron's image was not used in the current testing build I've been working on but I am sure if it's absolutely needed I could recreate the romm docker images using cloudron's base image.
Is it absolutely neccessary to be published that it uses cloudron's base image though?
-
Ah yes, all apps in the Cloudron app library would have to be based on the Cloudron base image. This has various reasons. Since our base image does have a lot of things pre-installed, you can probably try if using
FROM cloudron/base:4.2.0@sha256:46da2fffb36353ef714f97ae8e962bd2c212ca091108d768ba473078319a47f4just works? -
Ah yes, all apps in the Cloudron app library would have to be based on the Cloudron base image. This has various reasons. Since our base image does have a lot of things pre-installed, you can probably try if using
FROM cloudron/base:4.2.0@sha256:46da2fffb36353ef714f97ae8e962bd2c212ca091108d768ba473078319a47f4just works? -
@murgero do you have the source repo, if any for
mitchellurgero/romm:local-cloudron-changes?@nebulon I'm still rebuilding it to use the cloudron base image, currently my source tree (though not up to date) is https://git.cloudron.io/murgero/romm-cloudron. This is likely to change when the rewrite is done, waiting for upstream to merge a patch that fixes a crucial bug to get this working on cloudron.
