The trick is to switch to forgejo
Mental note: have to migrate my gitea instance over to forgejo.
I was aware of forgejo back when I first started hosting Gitea. Didn’t see much of a diff back then so I just went with arguably more popular option at that time.
About few months after it’s mostly just because I’m too lazy of a person.
Forgejo is a fork of Gitea. As of now I don’t think they have diverged much. So they’re (still) about the same. It was mainly created because of the takeover of the domain and trademark by a for profit company. Not because of different functionality.
The idea of “self-hosting” git is so incredibly weird to me. Somehow GitHub managed to convince everyone that Git requires some kind of backend service. Meanwhile, I just push private code to bare repositories on my NAS via SSH.
You’re completely missing the point. Even Gitea (much simpler than GitHub, nevermind GitLab) is much more than a git backend. It’s viewable in a browser, renders markdown, has integrated CI functionality, and so on.
Even for my meager self-host use-case, being able to view markdown docs in the browser is useful from time to time, even on my phone.
As for the things I use (a self-hosted) GitLab instance at work for… that doesn’t even scratch the surface.
Do you honestly think they’re “completely missing the point”? Read the meme. There’s no mention of gitea. Self-hosting git is nothing to wiggle your tie over. Maybe setting up the things you are talking about are, but git?
Bare repos with multiple users are a bit of a hassle because of file permissions. It works, and works well, as long as you set things up right and have clear processes. But god help you if you don’t.
I find that with multiple users the safest way is to set up/use a service. Plus you get a lot of extra features like issue tracking and stuff.
Agreed, which is why you’ll find in a subsequent comment I allow for the fact that in a multi-user scenario, a support service on top of Git makes real sense.
Given this post is joking about being ashamed of their code, I can only surmise that, like I’m betting most self-hosters, they’re not dealing with a multi-user use case.
Well, that or they want to limit their shame to their close friends and colleagues…
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters Git Popular version control system, primarily for code NAS Network-Attached Storage SSH Secure Shell for remote terminal access
3 acronyms in this thread; the most compressed thread commented on today has 14 acronyms.
[Thread #442 for this sub, first seen 20th Jan 2024, 16:55] [FAQ] [Full list] [Contact] [Source code]
I’ve got 3 tricks for ya:
- backups
- backups
- backups
What are you saying? My gitea is my backup!
I forked a piece of code and found a bug, I’m still afraid to merge it in because I might have hit it by mistake
I love it when I check out am applicants’ GitHub and run into a bunch of repositories with mods for hentai games.
I mean…are they good mods? Does the candidate have good code etiquette?
Honestly, the fact that a candidate would mod any game, let alone a hentai game, would be pluses in my book.
I definitely do not count it against them as long as they know how to human at the interview. I just review the code as I would any repo.
The only thing is that with regular projects I tend to go “I noticed on your GitHub you have project X that uses technology Y, etc etc”. With H projects I just go “do you have experience with Y” and let him choose how much he wants to share about the project. So far they remain vague on the non technical details and I let them leave with their dignity intact.
So, ranked, way ahead of candidates without visible projects, but slightly behind people with projects we can discuss in detail in front of the people from HR ;)
I self host gitea because I don’t want to pay Microsoft $160 a year.
Wait, isn’t github free?
codes
\facepalm
I was wondering if that might be a thing. Saw people talk about “the codes” instead of “code” more than once.
codes
