You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/doc/usage/backup-and-restore.en-us.md
+56Lines changed: 56 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -95,3 +95,59 @@ Repository Git Hooks should be regenerated if installation method is changed (eg
95
95
With Gitea running, and from the directory Gitea's binary is located, execute: `./gitea admin regenerate hooks`
96
96
97
97
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.
98
+
99
+
### Using Docker (`restore`)
100
+
101
+
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.
0 commit comments