From 816a1dacbf1f9fce2652d5402a74858e4cdcaf63 Mon Sep 17 00:00:00 2001 From: W Anders Date: Sat, 14 Sep 2019 17:55:48 -0500 Subject: [PATCH 1/4] Added admin cmd ref to backup-restore guide --- docs/content/doc/usage/backup-and-restore.en-us.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/content/doc/usage/backup-and-restore.en-us.md b/docs/content/doc/usage/backup-and-restore.en-us.md index 5cf2f4aec891d..cbcee8c4f5c6d 100644 --- a/docs/content/doc/usage/backup-and-restore.en-us.md +++ b/docs/content/doc/usage/backup-and-restore.en-us.md @@ -79,3 +79,9 @@ mysql -u$USER -p$PASS $DATABASE Docker), repository git-hooks should be regenerated. + +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. From a7956c1ac715cc13c728d15c29a2c22ffad4e4f4 Mon Sep 17 00:00:00 2001 From: W Anders Date: Sat, 14 Sep 2019 18:07:32 -0500 Subject: [PATCH 2/4] Clarified reason for command execution --- docs/content/doc/usage/backup-and-restore.en-us.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/content/doc/usage/backup-and-restore.en-us.md b/docs/content/doc/usage/backup-and-restore.en-us.md index cbcee8c4f5c6d..0eb897c97b2a0 100644 --- a/docs/content/doc/usage/backup-and-restore.en-us.md +++ b/docs/content/doc/usage/backup-and-restore.en-us.md @@ -80,8 +80,8 @@ mysql -u$USER -p$PASS $DATABASE Docker), repository git-hooks should be regenerated. +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` +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. +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. From f1e0b7a3593766e665667249aef844344a42f599 Mon Sep 17 00:00:00 2001 From: W Anders Date: Sat, 14 Sep 2019 19:09:50 -0500 Subject: [PATCH 3/4] Include directive for where command should be executed from Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> --- docs/content/doc/usage/backup-and-restore.en-us.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/doc/usage/backup-and-restore.en-us.md b/docs/content/doc/usage/backup-and-restore.en-us.md index 0eb897c97b2a0..5e2d897a0b14f 100644 --- a/docs/content/doc/usage/backup-and-restore.en-us.md +++ b/docs/content/doc/usage/backup-and-restore.en-us.md @@ -82,6 +82,6 @@ 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` +With Gitea running, and from the directory Gitea's binary is located, 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. From e73268a5225b9792313cb50af0e80767a16d5d81 Mon Sep 17 00:00:00 2001 From: W Anders Date: Sat, 14 Sep 2019 19:10:56 -0500 Subject: [PATCH 4/4] Be direct in consequences Co-Authored-By: guillep2k <18600385+guillep2k@users.noreply.github.com> --- docs/content/doc/usage/backup-and-restore.en-us.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/doc/usage/backup-and-restore.en-us.md b/docs/content/doc/usage/backup-and-restore.en-us.md index 5e2d897a0b14f..a3887bc64a632 100644 --- a/docs/content/doc/usage/backup-and-restore.en-us.md +++ b/docs/content/doc/usage/backup-and-restore.en-us.md @@ -84,4 +84,4 @@ Repository git-hooks should be regenerated if installation method is changed (eg With Gitea running, and from the directory Gitea's binary is located, 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. +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.