foster/forgejo
1
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-27 09:11:53 -05:00
Code Issues Wiki Activity
forgejo/docs/content/doc/developers/migrations.en-us.md
John Olheiser 1d6b565de4
Refactor docs (#13275) 
* First pass

Signed-off-by: jolheiser <john.olheiser@gmail.com>

* More changes

Signed-off-by: jolheiser <john.olheiser@gmail.com>

* Redirects

Signed-off-by: jolheiser <john.olheiser@gmail.com>
2020-10-23 11:59:45 -04:00

1.8 KiB
Raw Blame History

date title slug weight toc draft menu
2019-04-15T17:29:00+08:00 Migrations Interfaces migrations-interfaces 30 true false
sidebar
parent name weight identifier
developers Migrations Interfaces 55 migrations-interfaces

Migration Features

Complete migrations were introduced in Gitea 1.9.0. It defines two interfaces to support migrating repository data from other git host platforms to Gitea or, in the future, migrating Gitea data to other git host platforms.
Currently, migrations from Github, Gitlab, and other Gitea instances are implemented.

First of all, Gitea defines some standard objects in packages modules/migrations/base.
They are Repository, Milestone, Release, ReleaseAsset, Label, Issue, Comment, PullRequest, Reaction, Review, ReviewComment.

Downloader Interfaces

To migrate from a new git host platform, there are two steps to be updated.

  • You should implement a Downloader which will be used to get repository information.
  • You should implement a DownloaderFactory which will be used to detect if the URL matches and create the above Downloader.
    • You'll need to register the DownloaderFactory via RegisterDownloaderFactory on init().

You can find these interfaces in downloader.go.

Uploader Interface

Currently, only a GiteaLocalUploader is implemented, so we only save downloaded data via this Uploader to the local Gitea instance. Other uploaders are not supported at this time.

You can find these interfaces in uploader.go.