Romm V3.2.0 Error

Mister_ZeriOus · June 5, 2024, 3:38pm

After update and trying to figure out what went wrong it turns out they changed their repo name from zurdi15/romm to rommapp/romm. managed to fix this myself with your app edit script by changing image name. just letting you know as its a simple fix.

dragonfire1119 · June 5, 2024, 3:47pm

Thank you for letting me know.

This has already been updated here:

github.com

bigbeartechworld/big-bear-casaos/blob/4e044063bace5a2d7c1f1491e02e54af4e5bc26d/Apps/Romm/docker-compose.yml#L11


      
          # Configuration for romm setup
          
          # Name of the big-bear-romm application
          name: big-bear-romm
          
          # Service definitions for the big-bear-romm application
          services:
            # Service name: big-bear-romm
            # The `big-bear-romm` service definition
            big-bear-romm:
              image: rommapp/romm:3.2.0 # Docker image for the application
              container_name: big-bear-romm
              environment:
                - DB_HOST=big-bear-rommdb # Hostname of the MariaDB container
                - DB_PORT=3306 # Port used for MariaDB
                - DB_USER=romm-user # Database user for MariaDB
                - DB_NAME=romm # Name of the database (Should match the MYSQL_DATABASE value in the mariadb container)
                - DB_PASSWD=casaos # Database password (Should match the MYSQL_PASSWORD value in the mariadb container)
                - IGDB_CLIENT_ID=<IGDB client id> # IGDB client ID
                - IGDB_CLIENT_SECRET=<IGDB client secret> # IGDB client secret
                # [Optional] Enable user management and require authentication to access the interface (disabled by default)