this post was submitted on 10 Dec 2025
411 points (99.5% liked)

Selfhosted

53582 readers
699 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

By 'Git instances' they mean Gogs instances that allow open registration. I know most of the community moved from Gogs to Gitea, and then to Forgejo, but thought this was still worth noting.

you are viewing a single comment's thread
view the rest of the comments
[–] AmbiguousProps@lemmy.today 6 points 1 day ago (2 children)

I'm a current gitea user.. should I be moving to forgejo?

[–] victorz@lemmy.world 17 points 1 day ago (1 children)
[–] AmbiguousProps@lemmy.today 4 points 1 day ago (1 children)

Thanks! I'll add it to the todo list.

[–] klangcola@reddthat.com 3 points 1 day ago (1 children)

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 1 points 17 hours ago (2 children)

Doesn't Forgejo support SQLite as a backend?

[–] klangcola@reddthat.com 2 points 12 hours 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

[–] mko@discuss.tchncs.de 3 points 16 hours ago (1 children)

Yes, although MySQL/MariaDB or PostgreSQL are the more robust options.

[–] lambalicious@lemmy.sdf.org 1 points 15 hours ago (1 children)

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 2 points 13 hours 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.)

[–] jjlinux@lemmy.zip 1 points 1 day ago

Doesn't seem like Gitea has that issue, and just keep registrations disabled if possible and if your projects allow, avoid symlinking.