Documentation: Specify that you *need* to rename the executable

[yukijoou]

Feature Description

Currently, on the documentation for installing the binary version of gitea, the "Copy the Gitea binary to a global location" doesn't indicate that it is strictly necessary to keep a consistent name for the gitea binary, otherwise commit hooks break, and you can't push code anymore…

I kept the original name of the gitea binary from when I downloaded it (gitea-1.19.3-linux-amd64), and when updating, I named the new binary gitea-1.20.1-linux-amd64. This broke all the commit hooks. The only solution I can think of to fix this now is to write a sed script that does it on every repo on the server. This is a pain. Please warn against it in the documentation! The current (lack of) explanation makes it seem like giving the binary this specific name is left as a choice to the user, it is not!

EDIT: In case this happens to someone else, I fixed it with this script

#!/bin/bash

for file in $(find /var/lib/gitea/ -type f -wholename '*.git/hooks/pre-receive.d/*' -or -wholename '*.git/hooks/post-receive.d/*' -or -wholename '*.git/hooks/update.d/*'); do
	sed -i 's/gitea-1.19.3-linux-amd64/gitea/g' $file;
done;

Make sure to change 'gitea-1.19.3-linux-amd64' in the sed command to whatever was the name of your gitea binary!

Screenshots

No response

[techknowlogick]

Hi, there should be an automated startup task that rewrites those hooks. Also, if you need to rewrite the hooks there is an option to do so in the admin dashboard.
I'll leave this open as if your hooks aren't being rewritten then that could be a bug. Could you share how you've setup your install? I'm assuming systemd but are you also using the config provided in the documentation? Also, there is a system table in your database, could you share what the app path set in it is?

[yukijoou]

seems like my email response didn't go through… aah, tonight is not a good time for me to use a computer apparently lol

---

Hi,

Thank you, and no, the hooks didn't get re-written automatically… Maybe because I started gitea once before having all the repositories in place (I'm doing server migration at the same time -- things got a bit messy)

I didn't think to check the admin dashboard for that task though, I half assumed this wouldn't exist because it's not mentionned in the version update documentation… As for the install, yes, I'm using systemd. It's pretty much the config from this repo, I just enabled the dependency on postgresql, as that's what I use, and that's pretty much it…

I don't know how to check the database though, can you give me more precise instructions?

Thank you very much for your time!

[techknowlogick]

Ah, thanks for that clarification. I'm sorry if I missed this in your message above, but which DB are you using?

I suspect it's as you thought that since you were also migrating at the same time that the automated hook rewrite missed them. Either way I'll provide instructions to get the info requested above just to confirm.

[yukijoou]

I'm using postgresql! And thank you so much for your help!

[GiteaBot]

We close issues that need feedback from the author if there were no new comments for a month. 🍵

[wxiaoguang]

It should be a bug.

By design, Gitea should be able to update these paths automatically.

[techknowlogick]

@wxiaoguang as mentioned above, it didn't rewrite due to a migration happening at the same time, so the appPath saved in DB is the new one, and so when repos migrated with old path it wasn't updated.

[wxiaoguang]

I just recalled there is another one : Push failed with "Unable to find configuration file" #25633