Just some IT guy

  • 0 Posts
  • 55 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle





  • The developer working on federation plans to merge the changes into forgejo first and then from there into gitea but I’m not sure in how far the recent changes to gitea’s CLA have affected those plans.

    Forgejo is a drop in replacement (they are committed to keeping it that way for as long as possible) so, as far as I know, simply changing the gitea image to the forgejo image is all you would need to do.


  • They did start a cloud service for hosting Gitea which introduces a direct incentive for them to make Gitea less hosting friendly by, for example, making newly added configuration options less comfortable to set up. And more recently some changes to code contributions that are not exactly community friendly (as a result forgejo will be unable to upstream some of their changes)

    What lead to Forgejo, as far as I am aware, was less a problem that is already there and more the set of problems that have a very high chance of eventually manifesting, at which point forking the project would be too late.



  • Gitea is managed by a for profit which is now offering a hosting service. That alone is already a conflict of interest because one of Giteas core features is the easy self hosting.

    Then the contribution guidelines have been made stricter, anyone contributing now has to give up their copyright to the gitea management, meaning they could change the opensource license to a stricter one down the line without requiring community consent.

    The concern is that as time passes features will be locked behind a premium tier for self-hosters or the self-hosting itself will be made more difficult in an effort to push their cloud service.









  • As someone with a beef server: Nope, performance stays unsatisfactory. Redis helps a lot but only if the page is cached which tbh just makes the experience worse if the page isn’t cached

    Edit: I’m using the AIO installer though, as discussed elsewhere in this post that might be the root cause of the poor performance, will check on the weekend by installing nextcloud manually in a fresh vm