Thanks in advance for your help.
I am not an expert at all on the subject so forgive me if the information provided is not clear enough or if the subject is not in the right category.
I installed GITEA from the repositories (not from a docker container) on a fresh debian 12 server.
I manage to make it run correctly and adress it to my domain. It is up and running smoothly for a couple of weeks, and I tested my repositories and process without any issues.
I am now trying to keep my GITEA server up to date.
I manage to install the debian packages for automatic security updates, and now I am trying to update GITEA (no need for auto update but I want to have a clean and clear process).
As I understand based on my readings of the documentation the main steps of the process could be:
stop gitea instance
backup the database (gitea dump)
update the binary file found in usr/local/bin
restart gitea instance
A detailed list of acitons for the average user would be:
log on to the machine
open a terminal
change to the user running gitea instances (git in most cases)
download the new binary file and replace it in usr/loca/bin
When I am trying to do this I am never able to stop my gitea process :
When you installed from a Debian apt repository, you would keep it up to date with: sudo apt update && sudo apt upgrade
The method you referenced is for those who have done their own binary installation outside of host OS package management.
Despite being an apt fan, I went with a self-managed binary installation to better keep up with the pace of Gitea development. If you want more frequent updates than what Debian will provide, you may wish to do the same.
I installed from apt git maria-db nginx but not gitea.
So I am probably like yourself in “self-managed binary installation” and I also want to be able to follow correctly the versions to avoid security issues.
I don’t know that you need to specify the config file when you are using the default file.
Virtual hosts are managed similarly on nginx as in Apache. Assuming that you have defined your vhosts one per config file, you will only need to remove the corresponding symlink from the sites-enabled folder and reload nginx. Replace the symlink and reload to re-enable the site.