While the premise of setting up a self-hosted Git solution is intriguing (Gitea appears to be very fast too) but from an infrastructure perspective, will it not create an additional overhead to keep it highly available, maintain and/or upgrade?
PS: Just learned GitHub started offering private repos for upto 3 collaborators as per this
Yes, it requires operational overhead, as does any self-hosted solution.
This is useful, for example, for organizations seeking to control data flow (i.e. making this code only available on a private network, or to and from a CI/CD pipeline or deployment platform), or just anyone seeking to cease doing business with SaaS providers (my main motivation, for example)--cases where the operational overhead is not a compelling drawback.
Perfect! Concerns around privacy are very valid nowadays since all SaaS providers snoop on user-data in the name of rules & regulations, compliance via some way or the other.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.