Skip to content

Include git-hook regeneration in restore documentation #8181

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Sep 15, 2019
Merged

Include git-hook regeneration in restore documentation #8181

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
816a1da
Added admin cmd ref to backup-restore guide
wranders Sep 14, 2019
a7956c1
Clarified reason for command execution
wranders Sep 14, 2019
f1e0b7a
Include directive for where command should be executed from
wranders Sep 15, 2019
e73268a
Be direct in consequences
wranders Sep 15, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs/content/doc/usage/backup-and-restore.en-us.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,3 +79,9 @@ mysql -u$USER -p$PASS $DATABASE <gitea-db.sql
# or sqlite3 $DATABASE_PATH <gitea-db.sql
service gitea restart
```

Repository git-hooks should be regenerated if installation method is changed (eg. binary -> Docker), or if Gitea is installed to a different directory than the previous installation.

With Gitea running, execute: `./gitea admin regenerate hooks`

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 may fail.