4 ms·
I run Gitea myself as well. I generally throw in a new release once a month or so, never had any real hiccups.
by Deukhoofd 5y ago
I run Gitea myself as well. I generally throw in a new release once a month or so, never had any real hiccups.
- rolph 5y agoit sounds like you dont make code changes unless they are required for function.
- Deukhoofd 5y agoAlso for security reasons, and because some features are nice to have. But you're right in that I'm definitely not randomly updating sometimes. When I do update I basically just back up the database, throw in a new Gitea binary, and restart the service. As the releases have been fairly well tested in general, this hasn't given me issues so far.
- chockchocschoir 5y agoAgain, how much it actually change across those releases? GitHub most likely are going through more changes on a weekly basis (if not daily) than what Gitea does on a monthly basis.
- Deukhoofd 5y agoThe major releases generally change quite a lot in one go, for example: https://blog.gitea.io/2022/02/gitea-1.16.0-and-1.16.1-released/ https://blog.gitea.io/2022/02/gitea-1.16.0-and-1.16.1-releas... https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/ https://blog.gitea.io/2021/08/gitea-1.15.0-is-released/ But I'm sure Github changes a lot more. However, the question is if those changes are worth the instability. For my workflow I just want my repos to be accessible, have my source, issues, and wiki accessible, and of course my basic git operations working. If that core functionality is actually not working at times, I'd definitely consider changing the git provider.