Github is a double edged sword. Use it when you must, but you should self-host whenever possible.<\/p>\n\n\n\n
I started with For me though, After You can find a Gitea feature list here:<\/p>\n\n\n\n https:\/\/docs.gitea.io\/en-us\/comparison\/<\/a><\/p>\n\n\n\n Here's an old sysadmin rule of thumb: If it involves In all fairness, I spent a long time actually getting I would recommend So I spent far more hours than I'm proud to admit trying to get If you're just looking for a simple, self hosted https:\/\/github.com\/gogs\/gogs<\/a><\/p>\n\n\n\n Another nice \"self hosted\" option is cgit<\/a> but the default interface is very dated, and it's even more minimal than my ideal feature set.<\/p>\n\n\n\ngitlab<\/code> as it was the most popular github<\/code> alternative at the time, and I think for medium-large businesses hosting their own local, dedicated git instance, gitlab<\/code> is probably a good choice.<\/p>\n\n\n\ngitlab<\/code> wad definitely overkill. The upgrades get very complicated, and I'm ultimately just not a big Ruby on Rails fan... I just wanted locally hosted git<\/code> that I could also browse easily via http<\/code>, especially to graphically view older commits and branches, because every once in a while I do leave the terminal...<\/p>\n\n\n\ngitlab<\/code> my next solution was Gitea<\/code>, as I read it was a community fork of gogs<\/code> so I assumed it must be better... In hindsight, I would say Gitea<\/code> is working hard to compete with GitLab<\/code>. That's fine, but `GitLab` is actually what I wanted to get away from.<\/p>\n\n\n\nLDAP<\/code>, run the other way!<\/p>Me, screaming... every time I do something with LDAP...<\/cite><\/blockquote>\n\n\n\nLDAP<\/code> is necessary for directory based authorization and authentication. With lots of users, you're kind of stuck with it and so you better know how it works. Everything connected to X.509<\/code> is a whole different mindset than the rest of the Linux and Open Source movement. If software had an attitude, ldap software and the zshell would be at opposite edges of the attitude spectrum.<\/p>\n\n\n\ngitea<\/code> to work in my particular configuration, and just ended up dedicating way more time to it than I really wanted to. For me, git<\/code> isn't very much different from samba<\/code>... I just want it to work so I can focus on problems that I'm more interested in.<\/p>\n\n\n\ngitea<\/code> to anyone looking at gitlab<\/code> and vice versa. These two are very similar. I think that blindly running either of them in a container just because you can is asking for trouble though. Go through the manual instillation and know how to set things up from scratch. If you can't do that, you shouldn't run it, because you won't be able to fix it when things go wrong. You want a sysadmin that knows how to set these up and how to manage them, back them up, and fix problems along the way.<\/p>\n\n\n\ngitea<\/code> working in my particular environment, but when I decided to switch over to gogs<\/code>, I had it all working and my old repos migrated over within 30 minutes.<\/p>\n\n\n\ngit<\/code> server via `https` in 2022, I think that gogs<\/code> is what you are looking for.<\/p>\n\n\n\n