How to update Gitea to the latest version?

[SimonLab]

Gitea is updated frequently, https://github.com/go-gitea/gitea/tags What is the process to update the version deployed on Fly?

Does having the latest version define in fly.toml enough? (I think yes) https://github.com/dwyl/gitea-server/blob/9e33ad7756634b506813b6b3d35331e386cfae3f/fly.toml#L6-L7

How do we check the Gitea version on Fly to see if a deploy has updated the version?

• [ ] Update Readme to explain that Gitea version is updated automatically when running flyctl deploy as the Docker image get the latest Gitea` image version
• [ ] "We should investigate adding a "watcher" for the tag version on https://github.com/go-gitea/gitea/tags to trigger an update. Someone must have solved this problem already ... maybe we can use @dependabot" see https://github.com/dwyl/gitea-server/issues/6#issuecomment-1138311820

I'm currently experience slow query time when I push to a repository and was wondering if a new version of Gitea could fix that or if I need to investigate other paths

[SimonLab]

The version is displayed on the footer of Gitea:

We could try to redeploy to see if the version bump to 1.16.8

[nelsonic]

@SimonLab Yeah, I think it's enough to have :latest in the fly.toml file. however we don't currently have a way of automatically deploying the server when a new release/tag is made for https://github.com/go-gitea/gitea/tags

We are currently running Gitea Version: 1.16.7 on https://gitea-server.fly.dev/

I just did a manual deploy:

LOG_LEVEL=debug fly deploy --verbose

And it appears to have updated:

We should investigate adding a "watcher" for the tag version on https://github.com/go-gitea/gitea/tags to trigger an update. Someone must have solved this problem already ... maybe we can use @dependabot 💭

[SimonLab]

Thanks for checking the update @nelsonic I've done a bit more test related to "slow" push (https://github.com/dwyl/gitea-server/issues/6#issue-1249164996), and use directly the git push command line from the terminal combine with time:

We can see that the issue is linked directly to the gitea-server. We can test again later on if we upgrade the server "hardware" option on Fly

maybe some useful info from: https://github.com/go-gitea/gitea/issues/13706

[nelsonic]

@SimonLab it's very strange. perhaps we need a dedicated "git push round-trip time" issue here so that we can link to it and open a similar issue over on https://github.com/go-gitea/gitea/issues with full context/explanation. 💭