Rendered at 15:44:29 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
dogline 17 hours ago [-]
Remember, if all you need is a git remote to push to somewhere via ssh, `git init --bare` on your server should be available and is solid if you don't need a web interface. Now you've got something you can push to on a shared server.
Unless you really also want a web interface, issue tracking, et. al. Then, use any of these fine tools. Go wild!
unsnap_biceps 16 hours ago [-]
I don't really need the web interface, but the actions are useful. Automatically building updated docker images and software packages is enough to accept the gitea complications, but gitlab is way too heavy IMHO
SmasherEpilepti 16 hours ago [-]
You can do that via hooks. You could probably even manage to hook up a CI engine like woodpecker via hooks and do it entirely that way.
Gitea or Forgejo with actions is almost certainly easier, but it's possible to do it with pure git.
unsnap_biceps 15 hours ago [-]
Actions support running on times. Sure, I could wire up a Rube Goldberg of systemd user timers and user units that trigger on hooks or I can store some yaml in the repo and it just works (tm)(r).
Sometimes the juice isn't worth the squeeze, and for me, doing it all custom isn't worth it for my home projects.
spwa4 2 hours ago [-]
What's wrong with a server-side post-receive hook?
sublinear 12 hours ago [-]
That's an interesting perspective.
I feel like this is one of those topics where compromise is futile. I use GitLab at work and use plain git on personal projects. I don't like spending time on tools that aren't either teaching me or paying me.
broodbucket 16 hours ago [-]
It is kind of nuts how seemingly a generation of programmers came to think Git = GitHub
pjmlp 4 hours ago [-]
I miss the built-in server that mercurial has had for years (hgweb).
sandreas 11 hours ago [-]
Something like gitolite has the benefits of access control... act can hell with actions. But I like the webif approach
wasting_time 19 hours ago [-]
For anyone curious why they should choose one over the other:
Unfortunately, seems like this is Forgejo's best suggestion on how to compare the two: https://i.imgur.com/j1665QR.png. Not sure that page helps much if you're not already bought in to a free-software-absolutist mindset
stryan 18 hours ago [-]
I wish they had an actual feature comparison list. I've been trying to find anyone who can give me a list of non-trivial differences between the two; so far it's always either FUD about Gitea's governance and security structure or ForgeFed. The former has made me rather wary of the project[0] and the latter has been stagnate for years and I'm no longer convinced anything will come from it. Otherwise it's just silence.
Personally I thought Forgejo was doing better work on their actions runner for a while from casual changelog browsing but Gitea's been putting a lot of work into theirs. Otherwise it mostly still looks like a soft-fork in practice to me.
[0] Not that I'm thrilled with Gitea's semi-open-core setup and company but they make it seem like they're kicking puppies and dangling features over non-enterprise users head before snatching them away.
_g0xr 17 hours ago [-]
deleted
kevincox 17 hours ago [-]
Of course I wouldn't recommend taking the conclusion. But it is a valuable view of some differences that the Forgejo developers perceive as valuable.
DASD 19 hours ago [-]
Thanks! Currently going through this decision process myself.
GrayShade 19 hours ago [-]
I suggest browsing through the release notes of the last 4-5 versions to see what you like more.
tjoff 18 hours ago [-]
I'd argue project values, license and health are way more important.
yjftsjthsd-h 17 hours ago [-]
Release notes would inform my view of project health and priorities
p-e-w 15 hours ago [-]
The project’s values as well, much more so than any “values statement”. The proof is in the pudding, not in the marketing speak.
daneel_w 17 hours ago [-]
Would you also argue that the technical quality, efficiency, capacity, performance etc. of a piece of machinery, too, is way less important than the social and political values of its manufacturer? Say, a piece of medical equipment used in a hospital to keep a patient alive.
ulimn 17 hours ago [-]
I have a feeling that nobody will die (most likely) for choosing forgejo or gitea... Apples and oranges...
DASD 17 hours ago [-]
But from the downvoting, announcing evaluation of these is contentious. Oh HN!
ThePinion 19 hours ago [-]
> This release contains security fixes. To give everyone time to upgrade, details will be added to this post in about a week.
Is this something that has been happening for a while or a new trend due to LLM concerns? I understand the reasoning, it just made me do a double take because I haven't really seen that before.
e12e 5 hours ago [-]
That's quite annoying - "security fixes" - but no information if your installation is affected or not? (Eg: in a module that's disabled)?
Makes work harder for sys admins - little difference for black hats.
It's still a (<LLM> look at diffs in latest gitea release - find the patched security issues and write poc exploit for cve assessment) I guess?
QuantumNomad_ 18 hours ago [-]
With Gitea specifically or in general? A lot of different software has silently included security fixes in updates combined with other changes and then later revealed what security fixes were made or stayed quiet about it all together, since long before LLMs could analyze changes.
Security researchers and malware authors would reverse engineer software updates of proprietary software, and scrutinise source code changes of open source projects to find secretly shipped security fixes.
techknowlogick 18 hours ago [-]
(bias note: I am a project lead of Gitea) this approach is based on what peertube has been doing, and is being attempted as an alternative approach to what we've been doing previously due to feedback we've been receiving from the community.
entrope 16 hours ago [-]
Is not describing the feedback part of the feedback you got? You're kind of playing into Forgejo's narrative about governance.
stackghost 18 hours ago [-]
Bizarre policy. Any bad guys unaware of the security implications are analyzing the patch diffs as we speak, so this seems nonsensical to me.
IshKebab 18 hours ago [-]
Yeah maybe it made sense in the past, but not in the age of AI.
donbox 15 hours ago [-]
Why does Gitea uses (hosts on etc.) Github and not on Gitea.
ChrisRR 7 hours ago [-]
Welcome to the issue which has been open since 2017
Unless you really also want a web interface, issue tracking, et. al. Then, use any of these fine tools. Go wild!
Gitea or Forgejo with actions is almost certainly easier, but it's possible to do it with pure git.
Sometimes the juice isn't worth the squeeze, and for me, doing it all custom isn't worth it for my home projects.
I feel like this is one of those topics where compromise is futile. I use GitLab at work and use plain git on personal projects. I don't like spending time on tools that aren't either teaching me or paying me.
https://forgejo.org/compare-to-gitea/
Personally I thought Forgejo was doing better work on their actions runner for a while from casual changelog browsing but Gitea's been putting a lot of work into theirs. Otherwise it mostly still looks like a soft-fork in practice to me.
[0] Not that I'm thrilled with Gitea's semi-open-core setup and company but they make it seem like they're kicking puppies and dangling features over non-enterprise users head before snatching them away.
Is this something that has been happening for a while or a new trend due to LLM concerns? I understand the reasoning, it just made me do a double take because I haven't really seen that before.
Makes work harder for sys admins - little difference for black hats.
It's still a (<LLM> look at diffs in latest gitea release - find the patched security issues and write poc exploit for cve assessment) I guess?
Security researchers and malware authors would reverse engineer software updates of proprietary software, and scrutinise source code changes of open source projects to find secretly shipped security fixes.
https://github.com/go-gitea/gitea/issues/1029