Migrate from gitea to Forgejo #392

New Issue

Closed

opened 2022-12-17 11:27:08 +01:00 by muppeth · 3 comments

muppeth commented

2022-12-17 11:27:08 +01:00

Owner

Since the move of gitea to for-profit business model, and codeberg just annoucing their drop-in replacement fork, we should follow and switch back to free software
https://blog.codeberg.org/codeberg-launches-forgejo.html

Since the move of gitea to for-profit business model, and codeberg just annoucing their drop-in replacement fork, we should follow and switch back to free software https://blog.codeberg.org/codeberg-launches-forgejo.html

muppeth added this to the 12.22 - December milestone 2022-12-17 11:27:08 +01:00

muppeth added the

forgejo

label 2022-12-17 11:27:08 +01:00

meaz commented

2022-12-18 07:57:59 +01:00

Owner

When migrating from Gitea to the Forgejo release with the same release number (eg from Gitea v1.18 to Forgejo v1.18), all that is necessary is to replace the Gitea binary with the Forgejo binary (or change the container image).

As we're still using v1.17.3, we should wait for the v1.18.0 to be out to update it and then switch to Forgejo v1.18.

Here are the things to be done:

Update repo (PR: Disroot-Ansible/gitea#22)
Update cstate (PR: Disroot-themes/cstate_theme#2)
Update website (PR: Disroot/Website#410)

> When migrating from Gitea to the Forgejo release with the same release number (eg from Gitea v1.18 to Forgejo v1.18), all that is necessary is to replace the Gitea binary with the Forgejo binary (or change the container image). As we're still using v1.17.3, we should wait for the v1.18.0 to be out to update it and then switch to Forgejo v1.18. Here are the things to be done: - [x] Update repo (PR: https://git.disroot.org/Disroot-Ansible/gitea/pulls/22) - [x] Update cstate (PR: https://git.disroot.org/Disroot-themes/cstate_theme/pulls/2) - [x] Update website (PR: https://git.disroot.org/Disroot/Website/pulls/410)

👍 1