this post was submitted on 05 Nov 2023
110 points (98.2% liked)
Open Source
31223 readers
309 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's a bit of an unfair comparison - that's the GitLab instructions to install from source. Most people use a package (rpm, deb) to install GitLab.
The installation instructions for GitLab from prebuilt binaries is https://about.gitlab.com/install/, and that's significantly shorter.
That said, I think for most home applications, GitLab is hugely overkill.
Yes that's true. I guess what I wanted to point out is that GitLab has dependencies like Postgres, Redis, Ruby (with Rails), Vue.js... whereas Forgejo can use just SQLite and jQuery.
sqlite is not something one would use for a database with a lot of users, postresql or mysql/mariadb is a better choice in these circumstances. and i don't think having jquery as a dependency in 2023 is a positive sign. not sayibg the software is bad, it's just different.
Fortunately they were inaccurate, and it supports mariadb and postgre too.
In the documentation, they leave sqlite and mssql to the last places in the listings.
That's a red flag
Hopefully not, as sqllite is never in a prominent place among the other supported databases in the documentation
Forgejo can use PostgreSQL perfectly → https://forgejo.org/docs/latest/admin/installation/#postgresql-database
Looking at it, I see the following...
GitLab's deps:
Forgejo deps:
I am missing something?
I assume that's to build from source.
The times I've installed GitLab it's been a case of
dnf install https://.... The rest gets dragged in automatically.Well, this way they could install dependencies anyway just automatically, so you don't see them unless you read before accepting the installation. I still can read this:
And then:
So they do some magic here, the script just installs the repository, so I can't see exactly any dependency they are currently using.
Probably Forgejo/Gitea also uses such dependencies, but their Go counterparts which are statically built into the server binary.
If resource efficiency only depended on that, Gitlab would be more efficient with memory because of this. We all know that's not the case, I just said it as a comparison.
This also means that while Forgejo/Gitea depends less on your system installation, it also wont benefit from updated dependency packages.
If they maintain the binary properly, could cause less issues with dependencies compatibility, so it's less pain for the DevOps team, like a container image, just pull the new image and done.