Transition guide moving from Gitea to Forgejo #69

circlebuilder commented 2022年12月17日 08:50:05 +01:00

Mentioned in chat there are questions about transitioning from Gitea to Forgejo and in follow-up mention of offering a transition guide for people to go through this process. Sounds like a good idea to have this as a separate piece of documentation.

[Mentioned in chat](https://matrix.to/#/!qjPHwFPdxhpLkXMkyP:matrix.org/$_FLCYrKPSNwaZn0cdRzivIYC0wfacOfEVKN778Fie_8?via=matrix.org&via=tchncs.de&via=exozy.me) there are questions about transitioning from Gitea to Forgejo and in follow-up mention of offering a transition guide for people to go through this process. Sounds like a good idea to have this as a separate piece of documentation.

rdwz commented 2023年01月23日 09:08:13 +01:00

Yeah, definitely...

• Who has done an Forgejo update to a Gitea Installation? Any known problems or is it like any other Gitea update before?
• Manual preparation needed?
• What about the Rebranding that has been done partly, can this lead to problems in the future?

Yeah, definitely... - Who has done an Forgejo update to a Gitea Installation? Any known problems or is it like any other Gitea update before? - Manual preparation needed? - What about the Rebranding that has been done partly, can this lead to problems in the future?

KaKi87 commented 2023年01月23日 23:33:30 +01:00

Who has done an Forgejo update to a Gitea Installation?

I did.

Any known problems

None.

is it like any other Gitea update before?

Yes.

Manual preparation needed?

No.

Actually, I've read on some Forgejo documentation that some versions or circumstances may require additional preparation steps, but personally I never did, on any Forgejo/Gitea version ever.

> Who has done an Forgejo update to a Gitea Installation? [I did.](https://git.kaki87.net) > Any known problems None. > is it like any other Gitea update before? Yes. > Manual preparation needed? No. Actually, I've read on some Forgejo documentation that some versions or circumstances may require additional preparation steps, but personally I never did, on any Forgejo/Gitea version ever.

crystal commented 2023年01月24日 03:38:49 +01:00

Who has done an Forgejo update to a Gitea Installation?

I did too

Any known problems

Nope.

Is it like any other Gitea update before?

Yes.

Manual preparation needed?

Not needed. I had Gitea set up with systemd and most of the related directories, files, and services were named gitea. It works fine just leaving it like this, but I went ahead and renamed everything to forgejo, leaving behind symlinks to avoid breaking anything that I forgot to update.

> Who has done an Forgejo update to a Gitea Installation? [I did too](https://sc.cryxtal.org/) > Any known problems Nope. > Is it like any other Gitea update before? Yes. > Manual preparation needed? Not _needed_. I had Gitea set up with systemd and most of the related directories, files, and services were named `gitea`. It works fine just leaving it like this, but I went ahead and renamed everything to `forgejo`, leaving behind symlinks to avoid breaking anything that I forgot to update.

Ryuno-Ki commented 2023年02月27日 17:40:32 +01:00

• Who has done an Forgejo update to a Gitea Installation?

I did.

Any known problems or is it like any other Gitea update before?

Yes.

• Manual preparation needed?

Some aftermath. I had to put the forgejo binary (preferably without version number) next to the gitea one and adjust git hooks. Otherwise I will receive a rejection on pushes, because I deleted the gitea binary after the migration and it can't find the correct path.

I also wrote a new supervisord configuration for Forgejo (by now there is an instruction in the community curated Lab space of Uberspace).

• What about the Rebranding that has been done partly, can this lead to problems in the future?

Not in my observation yet.

> - Who has done an Forgejo update to a Gitea Installation? [I did](https://code.jaenis.ch). > Any known problems or is it like any other Gitea update before? Yes. > - Manual preparation needed? Some aftermath. I had to put the forgejo binary (preferably without version number) next to the gitea one and adjust git hooks. Otherwise I will receive a rejection on pushes, because I deleted the gitea binary after the migration and it can't find the correct path. I also wrote a new supervisord configuration for Forgejo (by now there is an instruction in the community curated Lab space of Uberspace). > - What about the Rebranding that has been done partly, can this lead to problems in the future? Not in my observation yet.