diff options
| author | kralo <kralo@users.noreply.github.com> | 2024-02-26 00:35:52 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-25 23:35:52 +0000 |
| commit | f13f93261ea7e5199a13f2c347ad2d45dbe75d4b (patch) | |
| tree | e500aa4ee92a05432eb874772e8e383dfe742142 /docs/content | |
| parent | 49e482674700e184aa84806acfb7edaae0554291 (diff) | |
| download | gitea-f13f93261ea7e5199a13f2c347ad2d45dbe75d4b.tar.gz gitea-f13f93261ea7e5199a13f2c347ad2d45dbe75d4b.zip | |
Improve Documentation for Restoration from backup (#29321)
Comment the default path for repos and suggest using doctor for when
things are stuck
Diffstat (limited to 'docs/content')
| -rw-r--r-- | docs/content/administration/backup-and-restore.en-us.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/content/administration/backup-and-restore.en-us.md b/docs/content/administration/backup-and-restore.en-us.md index d46efecf99..451ef5c944 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 @@ -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. |