Add checks when the binary is moved or other crucial changes

[guillep2k]

• Gitea version (or commit ref): 1.9.3

Description

Ref: #8208

If a user changes gitea binary location, the server seems to work initially, but fails later when users attempt to push commits.

We should have some check of where the server was installed the last time and update hooks and authorized_keys automatically or at least give the user some warnings.

Perhaps there are other nice checks that can be done at startup.

[lunny]

We could randomly chose one repository and generate a new script and compare it with that script on repositories to test if it's the same. We can give a warning information on console or admin UI or notification?

[bagasme]

@lunny warnings should be thrown on both console and admin UI.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[guillep2k]

I think this check should be done at the instance start. It could share some code with "the doctor".

[lunny]

@guillep2k if you have many repository, this operation will spend many time when start. I don't think it's necessary to check that when start. A doctor command should be better.

As I said, if you really want to check that, we can chose some of repositories randomly to check but not every one.

[guillep2k]

Yes, I just wanted to ping the stale-bot, sorry.

[lunny]

Aha, @Stale !