Doesn’t seem like Gitea has that issue, and just keep registrations disabled if possible and if your projects allow, avoid symlinking.
Comment on 700+ self-hosted Git instances battered in 0-day attacks
AmbiguousProps@lemmy.today 3 weeks agoI’m a current gitea user… should I be moving to forgejo?
jjlinux@lemmy.zip 3 weeks ago
victorz@lemmy.world 3 weeks ago
Yes, even without this current news.
forgejo.org/compare-to-gitea/
AmbiguousProps@lemmy.today 3 weeks ago
Thanks! I’ll add it to the todo list.
klangcola@reddthat.com 3 weeks ago
I just did it not long a ago. Gittea -> Forgejo10 -> Forgejo11 LTS, in Docker. Surprisingly quick, painless and smooth.
(My only issue was not Forgejo, but MySQL. Because the hardware is ancient and Docker compose pulled down a new version of mysql8 at the same time as pulling forgejo. New version of mysql8 didnt support my CPU architecture. Easy fix was to change the label mysql8oraclelinux7 in Docker compose and pull that image. There is a issue with solutions in the MySQL Docker GitHub repo)
lambalicious@lemmy.sdf.org 3 weeks ago
Doesn’t Forgejo support SQLite as a backend?