Hi. I self-host gitea in docker and have a few repos, users, keys, etc. I installed forgejo in docker and it runs, so I stopped the container and copied /var/lib/docker/volumes/gitea_data/_data/* to /var/lib/docker/volumes/forgejo_data/_data/, but when I restart the forgejo container, forgejo doesn’t show any of my repos, users, keys, etc.

My understanding was the the current version of forgejo is a drop-in replacement for gitea, so I was hoping all gitea resources were saved to its docker volume and would thus be instantly usable by forgejo. Guess not. :(

Does anyone have any experience migrating their gitea instance to forgejo?

    • poVoq
      link
      fedilink
      English
      48 months ago

      You have a very loose definition of “essentially”. I can see easily see multiple ways of the OP’s copy approach failing while swapping out the container in place would not.

      • Mike WooskeyOP
        link
        fedilink
        English
        18 months ago

        Can you share some of them so I might have an idea what to try to do differently?

        • poVoq
          link
          fedilink
          English
          28 months ago

          You need to share more details about your setup, but as others have already mentioned, it could be an database issue, because usually Gitea is configured to use a Postgresql database.

          Also make sure you don’t combine an upgrade with a migration, the Gitea and Forgejo versions need to be roughly the same. Especially around the 1.20 version there was a need to change the folder structure before upgrading.

          • Mike WooskeyOP
            link
            fedilink
            English
            18 months ago

            Thanks for that info. I did combine an upgrade (1.20 to 1.21) with the migrations, but I guess I lucked into it working. My problem was that the container’s path to the migrated gitea volume was incorrect.