Yeah I'm into Gitness
Gitness goddamn code to compile
this post was submitted on 22 Sep 2023
173 points (94.4% liked)
Selfhosted
39930 readers
419 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
You're down with the Gitness?
We're done. This guy wins the Internet. We can all go home now.
load more comments
(1 replies)
Looks interesting, although the comments about other git repo services being bloated, complicated, and resource heavy, followed by a paragraph about AI features that have been added, with more planned in the future, seems a touch ironic to me.
My first thought is that it's just an AI training move
Isn't the whole point of these things the "bloated" (CI/CD, issue tracker, merge requests, mirroring, etc) part? Otherwise we'd all be using bare git repos over ssh (which works great btw!)
It's like complaining about IDE bloat while not using a text editor. Or complaining there's too many knives in a knife set instead of buying just the chef knife.
Actually, I do use git bare repos for CD too. :) The ROOT/hooks/post-update executable can be anything, which allows to go wild : on my laptop, a push to a bare repos triggers deploy to all the machines needing it (on local or remote networks), by pushing through ssh to other bare repos hosted there, which builds and installs locally, given they all have their own post-update scripts ; all of that thanks to a git push and scripts at the proper paths. I don't think any forge could do it more conveniently.
For me the main interest of forges is to publish my code and get it discovered (before GitHub, getting people to find your repos hosted on your blog's server was a nightmare). Even for the collaboration, I could do with emails. That being said, most people aren't on top of their inbox, in which mails from family are mixed with work mails and commercial spam in one giant pile of unread items, so it's a good thing for them we have those issue trackers.
I find that claim so dubious. Like they list running on the smallest VMs as a feature but give no specific requirements for hosting or running the service. This whole article reads like buzzword salad. I question if the creators even know what a git forge is.
There hasn’t been a new Git repo launch in almost a decade
Am I the only person annoyed they seem to mistake repositories for forges? It's already annoying when casual users say "git" for "GitHub", but those guys actually want to build a forge, explaining they're going to do better than anyone else. Maybe start by properly using the terms?
And of course there have been forges launched, including SourceHut, Gitea, Gogs, Forgejo…
Gitea, Gogs, Forgejo
"They are the same picture."
Here I am knowing the difference between git and GitHub, GitLab, ...
But what's a 'forge' please ?
That's the name we use to designate software like GitHub, GitLab and similar, which provide repositories hosting and tooling like issue trackers. It's supposed to be named like that because of SourceForge, the oldest of such tools, although I didn't hear the term "forge" before the last 5 years or so, long after SourceForge demise, so I imagine there is a bit of nostalgia in this name (not sure who is nostalgic of SourceForge, though 😂). The wikipedia page : https://en.wikipedia.org/wiki/Forge_(software)
SOURCEFORGE: I'm not dead yet!
load more comments
(4 replies)
I myself have launched several new git repos in the last decade. Where's my article TechCrunch?
I complained when the term "crypto" was co-opted. Come die with me on this hill where we care about things.
Also plain wrong - Codeberg launched in 2019. Now the question is: did the author just not know better, or is he paid not to know?
Codeberg isn't an entirely new forge. It's just a well-known gitea/forgejo instance. Sourcehut would probably be a better example.
Thank you for the correction! Then it's also wrong due to Gitea which launched in 2016.
The worst part is that this is a direct quote from Harness' CEO, not from TechCrunch author. :) Maybe they have a great product, I don't know, but it certainly feels like an amateurish launch. :D
Yeah, if a CEO has to lie to make their product seem better, it's blacklisted in my mind.
I thought you were being overly pedantic but my god, they keep repeating the point. They seem to have no idea what the difference between a platform hosting code repositories and an individual repository is or even what version control software is. What the bloody hell is this.
load more comments
(1 replies)
Im amused that the repo for it is on github and not on, well, Gitness
total power move
Nobody name their new product Gitler for some reason. Such a good name.
The logo writes itself.
Gitea and Forgejo are the way to go. Especially Forgejo which is working on federation just like Lemmy but for Forgejo repos and instances.
I want gitea to get federation
AI? Not bloated? Mmm. Will stick with Gitea.
Seems fast compared to self-hosted GitLab or Bitbucket. I don't see a way to add an ssh key or gpg key for code signing. No dark mode so expect to burn your retinas out in the middle of the night. I'll wait until it's a little more fleshed out before thinking about replacing Gitea in my network, though.
So Gitlab
Gitlab takes way more RAM to run the docker container than i want. If this is lighter, that sounds nice. And im using only the most basic functionality, so wont be much loss to me if it cant do whatever fancy stuff.
How about Gogs? The whole thing is < 30 MB, and is lightweight enough to run on a Raspberry Pi. You can even get a native binary package if you want to run it without the overhead of Docker.
Gitea is in same lightweight category.
Gitea is a fork of gogs. Forgejo is a forge of Gitea too. I would suggest/use Forgejo.
Also hosted on… GitHub! 😀
well, shit, it looks like that is indeed what I want! setting it up now, thanks!
load more comments
(1 replies)
Gitea?
Fair. Competition is also good.
Especially if it's a competition to Microsoft.
load more comments
(3 replies)
Does someone have a link to an instance to view? I don't get why their code is hosted on Github
I disagree with this almost on principle. GitHub was a mistake. We don't need these large, bloated, isolated forges that are just going to be acquired and converted into social networks. Forgejo> is the future. Any new forge not even trying to support federation and independent hosting out of the box is dead in the water to me. You wanna build a github style accessible platform above forgejo go right ahead, the thing github did best was make all of this accessible.
i'm not finding a way to prevent creating users right now... i'm just able to register new users again and again on the docker run. maybe i'm just missing the config (the documentation is looking like it needs to be fleshed out).
not really trying to anyone with the url make an account on my basement computer...
view more: next ›