Comment on 700+ self-hosted Git instances battered in 0-day attacks
klangcola@reddthat.com 5 days agoI 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 4 days ago
Doesn’t Forgejo support SQLite as a backend?
mko@discuss.tchncs.de 4 days ago
Yes, although MySQL/MariaDB or PostgreSQL are the more robust options.
lambalicious@lemmy.sdf.org 4 days ago
If MySQL is more robust than SQLite of all things, something is going seriously wrong.
Then again, it’s 2025. I no longer bet on what to expect from reality. Next someone points me to a mail indicating linux kernel will move its bookkeeping to MongoDB.
JackbyDev@programming.dev 4 days ago
Depends how they define robust. MySQL has a myriad of features SLQite doesn’t have and won’t ever have. If they mean something like user configuration then SQLite is just out by default.
(Coming from a SQLite fan.)
klangcola@reddthat.com 4 days ago
To be honest I don’t remember why I set up gitea with MySQL instead of sqlite (or MariaDB), its quite a few years ago. And sqlite would probably be fine for my single-user instance