Assistance migrating from gitea to forgejo

lal309, 1 month ago (edited 1 month ago)

Okay so your post inspired me to make the switch. All I had to do was switch out the image to the forgejo one. Everything worked right away. To try to make things as clean as possible, I went ahead and renamed my bind volume paths and app.ini stuff from gitea to forgejo but no matter what I tried, once I started the container, the container would create a gitea directory with a new app.ini. I even tried to run the forgejo compose on another host and the app still creates a gitea directory within the bind mount. Am I doing something wrong. I understand it’s a drop in replacement but I’m sure there’s a way to get a cleaner cut over.

compose.yml

volumes:

• ./data:/data

Host directories

~/forgejo

• data - forgejo - renamed for the migration - git - ssh - gitea - gets created by the app no matter what I do or what paths are set in app.ini
• compose.yml

How do I keep forgejo from creating this gitea directory? Why doesn’t it create a forgejo directory???

Edit: gitea version was - 1.21.7 and forgejo replacement image is 1.21.7-0

mike_wooskey, 1 month ago

I don’t know if your problem is the same as mine was, but the symptom sounds the same.

The docker-compose.yaml file shown in the Forgejo documentation for docker installation shows this mount:

<span style="color:#323232;">    volumes:
</span><span style="color:#323232;">      - ./forgejo:/data
</span>

For me, Forgejo installed and created new resource files in /data and ignored the resource files gitea alread made.

I changed the volume to:

<span style="color:#323232;">    volumes:
</span><span style="color:#323232;">      - data:/var/lib/gitea
</span>

Forgejo then recognized the gitea resources.

lal309, 1 month ago

Not quiet. I was running gitea before so my mount was ./gitea:/data but since switching over to forgejo, I renamed my ./gitea directory to ./forgejo. Adjusted my compose file to have a mount of ./forgejo:/data.

Now inside of that renamed forgejo directory, there are a bunch of gitea references and even one more directory called gitea. When I migrated everything worked right away but since I wanted a cleaner transition, I renamed and switched all gitea references to forgejo but went I brought the stack back online, it went belly up.

As a troubleshooting step, I recreated my compose file and created a new empty ./forgejo on a different machine just to see what a new and fresh install would look like and the forgejo stack itself created all kinds of gitea references and gitea directory once I brought it up. So to fix my original deployment, I reverted all the references back from forgejo to gitea and everything worked again.

For fun, I went out to codeberg to look at the Dockerfile and saw that they had a bunch of gitea things within their own Dockerfile so nothing I can do for now

anzo, 1 month ago

No experience, but saw gorgeous has a guide to migrate. Their latest Blogpost states to do that ASAP coz they’re going to stop keeping the drop-in 1:1 replacement to advance in their cool feature set ;)

justdoitlater, 1 month ago

Why migrate from gitea to forgejo?

poVoq, 1 month ago

Why this backwards way of migrating? The recommended way to to replace the Gitea docker image with the Forgejo one and leave everything else in place. Maybe make a backup before that you can revert to in case something goes wrong though.

catloaf, 1 month ago

That’s essentially what they did.

mike_wooskey, 1 month ago

That is what I did. And it didn’t work.

poVoq, 1 month 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_wooskey, 1 month ago

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

poVoq, 1 month 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_wooskey, 1 month 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.

Oisteink, 1 month ago

Can you see the data you copied inside the container? I’m quite sure you either don’t have the volume mounted, or the config files refers to a different folder than the gitea one did. Did your gitea container store data in sqlite as you are copying raw files rather than migrating a database?

I’d go with lxc instead of containers if you don’t fully understand docker. Overhead isn’t much different and you get a “normal server” where you can drop in forgejo to replace gitea

mike_wooskey, 1 month ago

Can you see the data you copied inside the container?

That led me to my problem! I did have the volume mounted, but the container’s path was incorrect: Forgejo was recreating it’s resource files as a new install because where it was looking for them, they didn’t exist.

Thanks!

JASN_DE, 1 month ago

What are you using as a database? Also, from which Gitea version to which Forgejo version did you attempt the migration?

mike_wooskey, 1 month ago

Both gitea and forgejo are using sqlite3. Gitea 1.20.0, Forgejo 1.21.