Gitlab’s a great alternative too, it’s definitely more resource intensive than Gitea but their community edition is packed with features. A federated Git platform sounds intriguing…
I have been on/off gitlab for a few years but they do sometimes weird things that drive me nuts. For example last time i check you cant search a repo issues without logging in.
One of main things i use repo sites for is to troubleshoot and searching issues is a great way. Why put a barrier to that? I cant imagine it is a big server load. Just dickish.
You can search issues without being logged in, but that setting has to be enabled in a repo or group’s permissions (Settings > General > Visibility, project features, permissions). Project visibility has to be Public, and issues should be set to Everyone with Access. I think tissues are defaulted to private or internal by default.
Gitlab’s a great alternative too, it’s definitely more resource intensive than Gitea but their community edition is packed with features. A federated Git platform sounds intriguing…
Hm did they leave ruby on rails behind yet? Last time I set it up it ATE resources like there’s no tomorrow…
Ran it around Christmas - was still an intense resource hog. Lots of features and great for corps, but too much otherwise
I have been on/off gitlab for a few years but they do sometimes weird things that drive me nuts. For example last time i check you cant search a repo issues without logging in.
One of main things i use repo sites for is to troubleshoot and searching issues is a great way. Why put a barrier to that? I cant imagine it is a big server load. Just dickish.
You can search issues without being logged in, but that setting has to be enabled in a repo or group’s permissions (Settings > General > Visibility, project features, permissions). Project visibility has to be Public, and issues should be set to Everyone with Access. I think tissues are defaulted to private or internal by default.