From c25682ccc427bdab7e40dca9690fda50556aa216 Mon Sep 17 00:00:00 2001 From: kralo Date: Thu, 22 Feb 2024 15:23:48 +0100 Subject: [PATCH 1/2] Update help on backup-and-restore.en-us.md by default, repositories is a subfolder of data/ `%(APP_DATA_PATH)s/gitea-repositories` --- docs/content/administration/backup-and-restore.en-us.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/administration/backup-and-restore.en-us.md b/docs/content/administration/backup-and-restore.en-us.md index d46efecf99045..22cf6f5b6160e 100644 --- a/docs/content/administration/backup-and-restore.en-us.md +++ b/docs/content/administration/backup-and-restore.en-us.md @@ -92,7 +92,7 @@ cd gitea-dump-1610949662 mv app.ini /etc/gitea/conf/app.ini mv data/* /var/lib/gitea/data/ mv log/* /var/lib/gitea/log/ -mv repos/* /var/lib/gitea/gitea-repositories/ +mv repos/* /var/lib/gitea/data/gitea-repositories/ chown -R gitea:gitea /etc/gitea/conf/app.ini /var/lib/gitea # mysql From 6d04ab56a986923c7555547a11501f07473c24a8 Mon Sep 17 00:00:00 2001 From: kralo Date: Thu, 22 Feb 2024 15:27:17 +0100 Subject: [PATCH 2/2] Update backup-and-restore.en-us.md suggest running doctor after update, bare git repositories might throw ``` [E] RepoAssignment Invalid repo /var/lib/gitea/data/gitea-repositories/tester/testrepo.git: exit status 128 - fatal: not a git repository (or any of the parent directories): .git 2024/02/22 11:50:44 ...eb/routing/logger.go:102:func1() [I] router: completed GET /tester/testrepo for, 500 Internal Server Error in 5.4ms @ context/repo.go:425(context.RepoAssignment) ``` --- docs/content/administration/backup-and-restore.en-us.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/content/administration/backup-and-restore.en-us.md b/docs/content/administration/backup-and-restore.en-us.md index 22cf6f5b6160e..451ef5c944cf7 100644 --- a/docs/content/administration/backup-and-restore.en-us.md +++ b/docs/content/administration/backup-and-restore.en-us.md @@ -111,6 +111,8 @@ With Gitea running, and from the directory Gitea's binary is located, execute: ` This ensures that application and configuration file paths in repository Git Hooks are consistent and applicable to the current installation. If these paths are not updated, repository `push` actions will fail. +If you still have issues, consider running `./gitea doctor check` to inspect possible errors (or run with `--fix`). + ### Using Docker (`restore`) There is also no support for a recovery command in a Docker-based gitea instance. The restore process contains the same steps as described in the previous section but with different paths.