Migrate from Gitlab to Gitea #5

Open
opened 2023-01-27 22:51:49 +00:00 by therbron · 4 comments
therbron commented 2023-01-27 22:51:49 +00:00 (Migrated from git.halia.dev)

Now that Gitea supports container registry out of the box, it seems like the by-default choice, given how slow Gitlab can be in the current environment.

Now that Gitea supports container registry out of the box, it seems like the by-default choice, given how slow Gitlab can be in the current environment.
therbron commented 2023-01-27 22:51:49 +00:00 (Migrated from git.halia.dev)

assigned to @therbron

assigned to @therbron
therbron commented 2023-01-27 22:53:13 +00:00 (Migrated from git.halia.dev)

Currently, the main blocker was the profile heatmap being incomplete. This can be fixed by manually editing Gitea's database (straight forward action database) using the /users/{username}/calendar.json endpoint from Gitlab.

Currently, the main blocker was the profile heatmap being incomplete. This can be fixed by manually editing Gitea's database (straight forward `action` database) using the `/users/{username}/calendar.json` endpoint from Gitlab.
therbron commented 2023-05-29 15:47:05 +00:00 (Migrated from git.halia.dev)

A quick and dirty implementation of mass migration has been implemented: https://git.halia.dev/therbron/gitlab_to_gitea/-/tree/shell_rewrite?ref_type=heads

This includes issues, PR, and more.
So far, 2 manual interventions are needed :

  • SNIR MC cannot be migrated as it is too big, but this should be fixed by changing the repository's content
  • Organization images are not kept
A quick and dirty implementation of mass migration has been implemented: https://git.halia.dev/therbron/gitlab_to_gitea/-/tree/shell_rewrite?ref_type=heads This includes issues, PR, and more. So far, 2 manual interventions are needed : - SNIR MC cannot be migrated as it is too big, but this should be fixed by changing the repository's content - Organization images are not kept

The first step of the migration was completed yesterday.
The new organization has been updated with its original picture, and runners have been configured.

The aforementioned issue with SNIR MC has been fixed by rewriting history and backing up space taking directories in another way.

More migration steps will be required, as the initial step only went from docker to docker, not to kubernetes.

Follow up migration steps will add kubernetes deployment (production) and customization of some default Gitea assets.

The first step of the migration was completed yesterday. The new organization has been updated with its original picture, and runners have been configured. The aforementioned issue with SNIR MC has been fixed by rewriting history and backing up space taking directories in another way. More migration steps will be required, as the initial step only went from docker to docker, not to kubernetes. Follow up migration steps will add kubernetes deployment (production) and customization of some default Gitea assets.
therbron added the
Type: Enhancement
Priority: Medium
labels 2024-05-13 21:53:26 +00:00
therbron added this to the Halis cloud project 2024-05-13 21:53:28 +00:00
Sign in to join this conversation.
No description provided.