Please do not post a support request without first reading and following the advice in

Use GIT repository of roms for multiple Pi devices?

  • Hi all.

    I have a couple of Pi devices (Pi 3, Pi 1) with Retropie and all of them use the same ROMs.

    I'm getting tired of copying/updating ROMs manually (add new game, delete game, etc) and I was wondering if it would be feasible to maintain the roms in a local GIT repository, (in my NAS), clone it in /home/pi/RetroPie/roms and use "git pull" to update the romset in any of the Pis when desired.

    Appart from the ROMs themselves, is there anything in /home/pi/RetroPie/roms/ that I should exclude in a .gitignore file? Any configuration file is created there?

    Is there any flaw on this idea? Something I'm missing?

    (PD: I prefer not to store the roms in a SMB/CIFS share so that I don't depend of the network, but I like the idea of being able to update roms from a central repo).

  • Global Moderator

    There's a handy 'cloud' enabled saves storage script posted by one of the forum users - You can maybe adapt it for your needs; it's based on rclone(
    Other than that, git would be easy to implement, but it's a bit overkill for this purpose - unless you'd like to have a versioning system in place. A simple rsync script would suffice.

    As for the file types, I guess you'll have to think if you want to synchronize:

    • save states (*.state[X])
    • memory saves (*.srm)
    • artwork/gamelistst (media folder and/or gamelist.xml).

Log in to reply

Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.