Migrate repositories from a HTTP URL, local disk or SSH URL #22

New Issue

lunny · 2019-04-26T04:59:35Z

lunny commented

2019-04-26 04:59:35 +00:00

If we can implement a sub command migrate, that will be helpful.

# migrate from a http URL
tea --login=try migrate https://github.com/go-gitea/tea.git --name=gitea/tea

# migrate from local disk
tea --login=try migrate ./tea.git --name=gitea/tea

# migrate from a SSH URL, clone from ssh and then upload from local disk
tea --login=try migrate git@github.com:go-gitea/tea.git --name=gitea/tea

Author: @lunny If we can implement a sub command `migrate`, that will be helpful. ``` # migrate from a http URL tea --login=try migrate https://github.com/go-gitea/tea.git --name=gitea/tea # migrate from local disk tea --login=try migrate ./tea.git --name=gitea/tea # migrate from a SSH URL, clone from ssh and then upload from local disk tea --login=try migrate git@github.com:go-gitea/tea.git --name=gitea/tea ```

👍 1

lunny commented

2019-04-26 12:09:50 +00:00

Author: @noerw

I'm not well informed about the architecture, but afaik the gitea server implements migration logic for all these cases..
If so, the CLI shouldn't need to push from local disk, but trigger the migration on server side for the HTTP/SSH URL case.
This way the local clone can be made optional (with a --clone BooleanFlag?), which might be of interest for large automated migrations.

Author: @noerw I'm not well informed about the architecture, but afaik the gitea server implements migration logic for all these cases.. If so, the CLI shouldn't need to push from local disk, but trigger the migration on server side for the HTTP/SSH URL case. This way the local clone can be made optional (with a `--clone` BooleanFlag?), which might be of interest for large automated migrations.

lunny commented

2019-04-26 14:08:08 +00:00

Author: @lafriks

@noerw gitea does not implement migration from local path

Author: @lafriks @noerw gitea does not implement migration from local path

lunny commented

2019-04-26 14:08:53 +00:00

Author: @techknowlogick

@lafriks I think it does, but is disabled by default.

Author: @techknowlogick @lafriks I think it does, but is disabled by default.

lunny commented

2019-04-26 14:09:38 +00:00

Author: @lafriks

but from server disk but this would be way to migrate from users local disk

Author: @lafriks but from server disk but this would be way to migrate from users local disk

lunny commented

2019-04-26 14:18:17 +00:00

Author: @lunny

Yes, just like @lafriks said. This in fact will do three steps when migrate from local disk:

create a repo on gitea server
git add remote to that gitea server repo
push to remote server.

The original migration from disk will migrate from gitea server's disk but not guest's.

Author: @lunny Yes, just like @lafriks said. This in fact will do three steps when migrate from local disk: 1. create a repo on gitea server 2. git add remote to that gitea server repo 3. push to remote server. The original migration from disk will migrate from gitea server's disk but not guest's.

lunny commented

2019-04-26 14:21:06 +00:00

Author: @lunny

This command also could be some part of scripts to batch migrate local git repositories to gitea server.

Author: @lunny This command also could be some part of scripts to batch migrate local git repositories to gitea server.

lunny added the

kind/proposal

label 2019-06-09 13:39:09 +00:00

6543 self-assigned this 2019-11-08 03:24:35 +00:00

6543 removed their assignment 2019-11-08 03:24:36 +00:00

6543 self-assigned this 2019-11-08 03:24:56 +00:00

6543 commented