FYI: It looks like the latest version of Gitea (1.17.3
) requires Git 2.x; after upgrading, running ./stop
and ./start
did not actually produce any errors, but I was getting a gateway error when browsing the website. I eventually found an error in the logs (~/logs/apps/{gitea-app-name}/gitea.log
) saying as much about Git 2.x being required.
So, I used @sean's guide for upgrading Git (I'm on one of the CentOS 7 servers mentioned in this post) to upgrade to the latest version (2.39.0
), added $HOME/opt/bin
to my .bash_profile
, and ran ./stop
and ./start
again. The Gitea website was now working and checking the gitea.log
file shows that a migration happened. Hooray!
Not sure that this will work perpetually since only my .bash_profile
has the new git
binary available, so I'll just have to see if the website stops working after a long while. If it doesn't work, I've found that I should also be able to modify the path Gitea looks for Git by modifying ~/apps/{gitea-app-name}/custom/conf/app.ini
and setting the following INI values to configure Git, then stopping/starting Gitea again:
[git]
PATH = "~/opt/bin/git"