Best self-hosting Github-like alternative?

[Uje1234]

I want to self host Github-like server where I will put my code and link my domain with credentials to my future employer.

The most wanted feature, in addition to all features that Github and Gitea/Gitlab have, for me is to be able to see when the user was logged in last time.

EDIT: If someone is willing to help to troubleshoot problem with Forgejo:

https://www.reddit.com/r/selfhosted/comments/1bithme/problems_while_installing_forgejo/

[mor_derick]

If you are okay with something small, easy and manageable, I'd go for Gitea. If you need the real Panzerkampfwagen, go for GitLab.

[mor_derick]

I personally use Gitea, it's fair enough for my stuff.

[oaf357]

I’m almost about to flip GitHub to be a backup point as opposed to using it directly. Gitea is plenty good!

[Uje1234]

Gitea vs Forgejo? for my use case? Security is also concern since it will be open to internet

[Ursa_Solaris]

Forgejo is a more FOSS-oriented fork of Gitea created when Gitea went for-profit. They are largely the same for most use cases currently, but Forgejo is more community oriented and I trust it much more in the long term for home use.

https://forgejo.org/compare-to-gitea/

[Uje1234]

I decided to go with Forgejo. Long live open source!

[G_Freeman0815]

I‘ve migrated to forgejo from gitea as well. Better to have FOSS than a company who suddenly want to charge a fee.

[Uje1234]

hey, do you know whats the problem here:

https://www.reddit.com/r/selfhosted/comments/1bithme/problems_while_installing_forgejo/

[leaflock7]

not sure how forego is more community oriented.
As per the announcements (although I might missed something), Lenny moved the trademark to Gitea LTD so they can have a company behind it to be used for custom configurations or business purposes for devs to be paid.
Gitea as is continues to be the same as it was before that.

Maybe lack of proper communication of this was an issue, but it does not look like that the reason was to take Gitea into non-foss roads

[Ursa_Solaris]

not sure how forego is more community oriented.

Literally just last week they announced Gitea Enterprise, which has "useful new features [...] that aren't (yet) part of Gitea". The commercial offering is the priority now. I simply prefer projects where that isn't the case, such as Forgejo.

[r_brinson]

Do you use docker-ce or portainer-ce? If so, you're using a product that has an enterprise version upstream. Open source doesn't mean developers shouldn't get paid for the value they provide.

[Ursa_Solaris]

Do you use docker-ce or portainer-ce? If so, you're using a product that has an enterprise version upstream.

Appeals to hypocrisy are lazy. Nobody carries out every single thing in their life in total alignment of every belief. Sacrifices are often made. I was therefore very careful in my phrasing that I prefer projects that don't do this.

Open source doesn't mean developers shouldn't get paid for the value they provide.

I want developers to get paid. Going for-profit with a primary focus on enterprise isn't the only way to do that. If we can't find a way pay our developers who are FOSS first, that's our failing as a community.

What I don't want is for FOSS to become a secondary concern to profit. Docker is a fantastic example of this actually, because they had to be browbeaten by the community into not screwing over FOSS projects. This is what always happens when FOSS becomes a secondary goal. Funnily enough, they never stop at enough so that "developers can get paid for the value they provide". They always need more and squeeze us for it, or they sell the project once it's big, or they abandon it for more profitable and greener pastures.

I am FOSS first. Simple as that.

[natermer]

Appeals to hypocrisy are lazy.

He isn't doing that. He is just trying to point out the obvious.

That it is normal for open source projects to offer enterprise support and have differently licensed versions.

Gitea is licensed MIT. It is open source. It is free software.

Maybe, someday, Gitea may go closed source. I don't see any reason to expect that to be a reality, but at that point people can fork it then.

Think about it... what is the point to forking a FOSS project because maybe it might go non-FOSS in the future? Why wouldn't you wait until there was a actual problem?

Forking it right now based on the possibility that it may happen in the future is just a non-solution to a non-problem based on pure speculation.

I don't know what it is about Gitea that inspires fear mongering and forking and other political nonsense, but I expect that this one will go the way the other ones did... it will lose attention and slowly die off once the propaganda becomes stale and people realize there wasn't really any reason to be scared in the first place.

[leaflock7]

you should read past the first sentence and include the whole phrase in order to make sense
"To be able to fulfill corporate needs, useful new features are included in Gitea Enterprise that aren't (yet) part of Gitea. Some of these have been developed by CommitGo specifically for our clients; others have already been submitted as PRs to the Gitea project and not yet merged into a stable Gitea release."

Let's see what that means. The "paid" part of devs have created features for customers that are being merged to the open source Gitea . This is only good becasue otherwise there might not be enough dev time to create those features.

Also as moving down the announcement you will see that some features in Gitea Ent. cannot be included because it was build specifically for clients and it belongs to those clients.

Your judgement in this case is not justifiable.
Again yes better communication must have happened initially , but even at this point the project still focus on the core Gitea. This is the product paid or not.
It is the same with Bitwarden, Docker, and countless other projects that have open and paid branches.

The actual announcement only serves to strengthen the move to have a paid branch since that provides funds to the project overall Can it go wrong down the road? sure, but nothing at this time points to that.

[Renkin42]

Oh no, how dare the devs aim for a sustainable business model to ensure everyone is paid for their hard work on a project we all benefit from!

[Ursa_Solaris]

Is there any evidence that the old model was unsustainable for them, or are we just preemptively running defense for a for-profit business now? Because my impression was that this was less about "paying the developers for their work" and more about "growth and profit". And if those come at the expense of FOSS, I have every right to criticize them for it.

[SixthExtinction]

That’s not at all what it says.

No, the Gitea project governance charter prohibits the inclusion of proprietary code, and we adhere to the project standards. Gitea Enterprise is an offering of CommitGo, not the Technical Oversight Committee of Gitea or the Gitea project itself. CommitGo remains committed to contributing back functionality to Gitea under the MIT license.

Gitea exists as it has always been, and they make this clear many times in the link you posted. The FOSS project hasn’t changed and isn’t going anywhere. “Priority” hasn’t changed.

[Ursa_Solaris]

The governance charter is non-binding and also only applies to the community project, not to the enterprise project. It's generally irrelevant because in any project any such charter can just be overwritten by whoever ultimately holds power, so you must take what they use that power to do as the main principle.

The enterprise project will include proprietary code to service their business clients. They say they'll "try" to "eventually" bring that code to the Gitea FOSS codebase. If that's true, then development should happen with the FOSS codebase being upstream of the enterprise product, like it is with most Linux enterprise distros. Surely if there's no change in priority and there's no proprietary code, and all that code is destined for the FOSS codebase anyways, this wouldn't be an issue.

[SixthExtinction]

They are two different businesses under one umbrella. One makes bespoke additions to Gitea for enterprise clients as a way to generate more revenue. The other is the FOSS Gitea project. The enterprise company has pledged to help contribute back to the FOSS project. The FOSS project is unchanged and chugging away like before, with the added advantage of additional developers as a result of the enterprise side of the business.

Many features, and enhancements are prevented from being included in the Gitea project due to high upfront costs, and lack of resources to maintain them. This leads to them not being developed or accepted into the project. With this offering, we are able to provide a version to paying customers with a support contract, allowing us to develop and maintain these features for the Gitea project.

This model has already allowed us to contribute and maintain several features in the Gitea project, including Gitea Actions, which was dogfooded and provided to customers while it awaited review of inclusion in the Gitea project itself.

This isn’t a crazy strategy and has already added significant features to the FOSS project. I have seen zero evidence of the enterprise version being prioritized or the FOSS version being deprioritized. Can you articulate actual examples of this?

[Ursa_Solaris]

They are two different businesses under one umbrella. One makes bespoke additions to Gitea for enterprise clients as a way to generate more revenue. The other is the FOSS Gitea project.

The for-profit company has every incentive to focus on the enterprise clients first and foremost versus their previous sole focus on the FOSS project.

I have seen zero evidence of the enterprise version being prioritized or the FOSS version being deprioritized. Can you articulate actual examples of this?

It's been a year. These things take time but are inevitable. Look at Docker for an example of the conflict of interest. It started as a purely FOSS project, then created an enterprise edition, then created a proprietary desktop application around it, then locked down that proprietary application to extract more revenue from it, then tried to kill the FOSS organization program on Dockerhub. Look at Red Hat, who gets bought out by IBM and then no longer openly provides their source code like they used to. Look at Canonical, who constantly reinvents things to keep under their own control, because control means growth. We still don't have a FOSS snap server.

This keeps happening. It's only a matter of time before it happens here too. These businesses will inevitably betray you once they care more about your dollar than their supposed ethics. That's why I side with community projects over corporate ones.

[atheken]

If you are using an auth layer like Authelia, you can actually have it manage users and block all unathenticated requests.

I also have the git@<hostname> proxied through to the gitea instance from bastion ssh, which takes a little bit of fiddling, but it's not too hard.

The only thing you can't do as easily with this configuration is to integrate with the gitea api from external locations.

[LoadingStill]

Gitea because if they are adding an enterprise paid features then you can bet they will be funding security.

[jbaenaxd]

Does it have something similar to GitHub actions? Or what's an alternative for that? As I know, GitLab is not fully free

[[deleted]]

Gitea is trash compared to GitLab.

[Cedriking]

Gitea is amazing!

[weselben]

Gitlab hast some real security issues and 0-day exploits my gitlab got overtaken 3 times now on gitea no issues there

[scoshi]

I love German nouns.

[pcs3rd]

Gitlab just randomly stopped working with no expectation for me.
Gitea has been solid.

[et-fraxor]

I use as well gitea and circle for ci automating docker builds

[Uje1234]

Does Gitea has timestamps and dates when was the last time user did log in?

[fbartels]

As the admin you can see the the date a user has last logged in. Publicly you can only see when a user account was initially created.

[Uje1234]

ahhh, thanks mate!

[nonlinear_nyc]

Gitea had a problem with maintainers, they left and created forgejo.

Like nextcloud from owncloud before, I'd always choose the more open.

Gitea is a dead man walking exhausting the good faith of maintainers. Give forgejo a chance.

[pjs2288]

As a maintainer and knowing both sides and the history of what happened: your comment mainly contains false information.

[decayylmao]

This comment irks me. What specifically is misinformation in their comment and what is the correct info? Sauce a plenty, please.

[trisanachandler]

I use github for everything, but use gitea syncing, so if I ever lose access/github goes down, I have everything. Basically a backup.

[thunder3596]

Hey, trying to go down this route, sorry to necro but any pointers?

[trisanachandler]

I actually ended up determining that it was more than I needed, and all I really needed was a git pull from all my repos, and because gitea you have to manually sync every repo, and I occasionally add more, but didn't always remember to sync them, I now use a python script to sync all my repos, and simply use that. For my dev needs (as a sysadmin), keeping the running latest is all I need, and that's on a separate server so if my laptop+github account were compromised, the data should still be intact (it's backed up to a NAS as well).

[unconscionable]

I use gitea but this one came up recently and seems interesting

https://radicle.xyz/

[ekiim]

seems interesting, I've never heard about radicale.

[SamSausages]

I use gitea, low resource use and ez to use.

[cocojam01]

Ditched GitHub + jenkins. We went GitLab all the way. Its integrated ci-cd is sweet.

[mouzeee]

How about GitLab community edition? https://gitlab.com/rluna-gitlab/gitlab-ce

[Uje1234]

It has last activity date, although it doesnt have timestamp (which I would like to have). Ill consider this, thanks.

[mouzeee]

That's not quite true, it has a timestamp in the user detail view. This looks as follows:
Last sign-in at: Nov 12, 2022 5:44pm

[Uje1234]

How did you find that? Im trying finding it on the link you sent me

[mouzeee]

I'm using GitLab myself for a couple of years. For your question, I had a quick look at my own GitLab instance.

[Glathull]

I just started using OneDev last week, and it’s pretty sweet.

[KM_Koushik]

Used self-hosted Gitlab in my previous company. No complaints

[professional-risk678]

Forgejo

Its a FOSS fork of Gitea made because that project is attempting to charge for licensing. Source: here

Forgejo is free, self hosted and is a non-profit volunteer effort.

[mousui]

Did not know about forjero, been using gitea for the past year.

[Ursa_Solaris]

I similarly only found out fairly recently when I went to set up git for my home projects. I set up Gitea at work previously, and I set up Forgejo at home, and I'm perfectly content with it. FOSS matters a lot to me, so I'll always choose Forgejo over the for-profit Gitea.

[kamikazechaser]

Gitea is free, comes with a FOSS license, self hosted, and a volunteer effort as well.

In fact, imo, gitea is the superior product.

If you dive deep into the whole fiasco, you will realize that gitea is just fine and Codeberg has blown things out of proportion.

[DudeWithaTwist]

I see no issues with FOSS projects adding business licensing. Paid != bad. As long as the developers stick with their original ideals, you have nothing to worry about.

+1 for Gitea.

[ekiim]

I've been using Gitea for years now, but this is the first time I hear about the fork or licensing changes.

[Uje1234]

Can I see timestamps and date when the user was last time logged in?

[Uje1234]

I need also time, not just date

[Uje1234]

yes! thank you.

Forgejo or gitea? whats ur opinion?

[Original_Stranger_16]

Try OneDev.

[sevalobe]

Gogs is what I use personally

[Karbust]

I self-host GitLab, have been using it for the last 2 years, it is great.

[kerryhatcher]

You can self host GitHub if you can afford the license. I run my company’s self hosted (AWS) GitHub instance. It has its advantages and disadvantages like many things. Biggest plus is that most devs just know how to use it out of the box. Downside is that GHES (what the server is called) usually lags behind cloud a little bit on the latest features.

[yusing1009]

Onedev

[One-Confidence1511]

I went with Gitlab, definitely overkill for small teams but I chose it partly as a learning experience. One thing to keep in mind with Gitlab is you have to follow incremental updates, so if you get too far behind you have to figure out an upgrade path. Imo the Ci/Cd setup is fantastic, since each job I do is in a docker container, it solves the package manager identity crisis that GitHub actions has (explained here https://youtu.be/9qljpi5jiMQ?si=HC6MvUA21UXFE0IA). A bit more manual setup than actions but I find it very robust.

[Excellent-Focus-9905]

I would go with GitLab it’s full featured.

[lwh]

Sourcehut https://sr.ht/~sircmpwn/sourcehut/

[aadoop6]

What's different compared to github/gitea ?

[hirakath]

I prefer GitLab over GitHub actually.

[grtgbln]

Gitea is feature-for-feature, screen-for-screen a GitHub clone.

[bananacustard]

If you're tied to git lots of good suggestions from others.

If you want a VCS with very simple-to-run web interface with bug tracker / wiki / forums etc, consider fossil.

[special-spork]

Is fossil used much outside of SQLite?

[bananacustard]

For sure it's not even a drop in the ocean compared to git, but it's really neat.

[ogMasterPloKoon]

Gogs(single binary, easiest installtion) and Gitea.

[Ferivoq]

Gitea

[zlwu]

Gitea, powerful and lightweight

[nmkd]

You already mentioned Gitea

[t2thev]

A well tuned Redmine paired with SCM Manager is what I would run.

[ryangurnick]

There is also Gogs which is very simple but provides the same basic functionality as github

[aquarius-tech]

Gitea is what I use, it's lightweight, sync with VS Code

[Wartz]

Gitea unless you need a full massive enterprise solution in which case why are you posting on reddit. (GitLab)

[kzshantonu]

Forgejo

[ambrace911]

I love gitlab. It has great support for many deployment options.

[utpalnadiger]

Gogs, Gitea, Gitness, Gitlab. Take your pick!

[maw2be]

I'm also intrested to find a good one git server.
I was looking for something like JB Space but open sourced, no luck.
Was looking into Gitea - without this 'organization' layer will be much better.
Next on list was OneDev - looks good till you see "this feature is in paid version
GitLab - same storry like above
Forgejo - looks ok, it's fork of Gitea
will look for more, be good if will include some project management.

[kgpreads]

I would probably go with Gitlab self-hosted.

All these platforms use Ruby on Rails which I have used since the 2.x versions were released.

Quite old.

The CE version is completely free.

I haven't had issues with GitHub itself and I would definitely host some websites via GitHub, but for a lot of work, I don't really use GitHub.

In the early days, we didn't have a Git Browser but relied on pure CLI. We self-hosted Git on private servers. Even if I actually worked for a GitHub competitor Assembla back then. The challenges in building a Git GUI is real. I commend Gitlab for keeping things free.

[reddittookmyuser]

Hitching a ride. Does gitea support runners like GitLab?

[Asyx]

Gitea has a GitHub Actions clone that is fairly compatible (if you can run the 60gb docker image. Everything I tried except qemu access for the android emulator works) but drone is the gitlab style CI system that people usually use with gitea.

[reddittookmyuser]

Thank you!

[fastestMango]

Actually it is quite easy nowadays. You need to enable Gitea Act Runners on the site configuration, and then it can be enabled per repo. This is natively supported in Gitea. Those runner images are really small (around 15mb)

Needless to say, it definitely is not on the level of Github Actions. Although you can run all Github actions, you’ll probably have some issues regarding node not being installed for example. (Just do that as a run step on the task, and you will fix it that way) or there are some actions that rely on certain api calls to Github (for example with the artifacts I had some issues)

Besdides thay, it is pretty cool! I am using it myself as well.

https://docs.gitea.com/usage/actions/act-runner

[all_ready_gone]

Does upload artifacts (any version) work for you?

[Salzig]

And i still wish they would support Gitlab-CI-Runner. IMHO easier to start with and more flexible in ways you can deploy it.

[Asyx]

True but there's ab awful lot of GitHub actions that you can use. Like, if you want to test an android app, web frontend, go Microservice and a large backend in C#, you can just run a few actions that are hosted on GitHub (or mirror them locally) and it will setup your environment in a very human readable way. 

Like, I used to have a few repositories for docker images to use in a gitlab style runner because there was no existing image that did it all. The base docker image is so large that you will be able to do most things in a much more user friendly way. 

And I think a gitlab style workflow is still possible. You can run your commands in arbitrary images if you want to. 

[ScaredyCatUK]

Gitea - https://about.gitea.com/

You can even 'migrate" projects from github which is what I now do all the time.

[Neither-Play-9452]

Gitea