Closed mangeMelon closed 1 week ago
So two things.
Migration approach The image highlights a protection mechanism that exists as a precaution. On the new machine app.ini, set ALLOW_LOCALNETWORKS = true https://docs.gitea.com/next/administration/config-cheat-sheet#migrations-migrations
backup-restore. Since you own both machines and have filesystem access, a dump and restore might be a quicker method. https://docs.gitea.com/next/administration/backup-and-restore
So two things.
- Migration approach The image highlights a protection mechanism that exists as a precaution. On the new machine app.ini, set ALLOW_LOCALNETWORKS = true https://docs.gitea.com/next/administration/config-cheat-sheet#migrations-migrations
- backup-restore. Since you own both machines and have filesystem access, a dump and restore might be a quicker method. https://docs.gitea.com/next/administration/backup-and-restore
设置了 ALLOW_LOCALNETWORKS = true 仍然不行:
[migrations]
ALLOWED_DOMAINS =
ALLOW_LOCALNETWORKS = true
SKIP_TLS_VERIFY = true
BLOCKED_DOMAINS =
经测试,ALLOWED_DOMAINS 设置为空不行, 必须设置具体的域名才可以
[migrations]
ALLOWED_DOMAINS =
ALLOW_LOCALNETWORKS = true
SKIP_TLS_VERIFY = true
BLOCKED_DOMAINS =
经测试,ALLOWED_DOMAINS 设置为空不行, 必须设置具体的域名才可以
[migrations] ALLOWED_DOMAINS = ALLOW_LOCALNETWORKS = true SKIP_TLS_VERIFY = true BLOCKED_DOMAINS =
set ALLOWED_DOMAINS = *
problem resolved
Description
https://forum.gitea.com/t/migrate-repository-gitea-to-another-gitea-server/8761?u=mlebon Hello community,
OLD SERVER debian 11 gitea 1.19.4 -> gitea 1.21.7 mariadb Ver 15.1 Distrib 10.5.19-MariaDB nginx NEW SERVER debian 12 gitea 1.21.7 mariadb Ver 15.1 Distrib 10.11.6-MariaDB
My two systems communicate PING and SSH in both directions, and they are both self-hosted.
As part of a proof of concept I set up a Gitea server. Due to availability issues, this POC had to be functional.
Today I was able to configure a new Gitea server. I therefore want to transfer part of the deposits to the new server while maintaining the pull-request issues.
I see that in "new migration" the choice of gitea is available. I made several attempts without success, I tried with or without access token, mirror, LFS...
For the token I created it using the web interface of the old server profile -> configuration -> application I put a name and check all the permissions
Here is my installation procedure: So I use the migration tools selection Gitea. I put the URL of the repository that I want imported I fill in with an access token that I created I check the element labels tickets requests for addition, publication, milestone I select the new owner fill in the name of the repository and press migrate
and I get the following message
The configuration of the app.ini file is similar for both servers, I tried several configurations
New server log
While searching on the net I came across solutions consisting of dumping the database and copying the directory /var/lib/gitea
if possible I would prefer to be able to migrate the repositories
Screenshots
Gitea Version
1.21.7
Can you reproduce the bug on the Gitea demo site?
Yes
Operating System
debian 12
Browser Version
chrome Version 122.0.6261.113, firefox