When comparing GitHub Enterprise vs Gitea, the Slant community recommends Gitea for most people. In the question“What are the best self-hosted web-based Git repository managers?” Gitea is ranked 2nd while GitHub Enterprise is ranked 8th. The most important reason people chose Gitea is:
Easy to install and setup. Can run on a VPS with 1 core CPU and 256MB RAM.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Nice and usable UI
GitHub's UI is clean and intuitive. Each view is designed to not fill the screen with useless information.
For example, the repository view displays only the most crucial data about that repo - on the top it displays the number of commits, branches, releases and contributors. When clicked, each of them will take the user to a page that displays more detailed information.
Pro Support for various cloud hosting platforms
GitHub enterprise is available for Amazon AWS, VMware and now on OpenStack KVM as well.
This facilitates the use of GitHub Enterprise for people already familiar with these platforms and allows teams to keep using their infrastructure of choice.
Pro JIRA integration
When linked to JIRA, branches, commit messages and pull requests can all reference JIRA issues. This allows JIRA to display information about your development activity in the corresponding issue.
Pro Powerful search functionality
GitHub Enterprise has powerful search features that allow users to search by file name or project name. It's one of GitHub's most powerful tools.
Pro LDAP support
GitHub has improved the LDAP performance. By optimizing searching strategies, they have reduced significant network IO and total queries. Therefore, in some cases as much as 40 percent less data is transmitted on sign on.
Pro Gists support
Gists are ways to share code or have conversations about anything without needing a full git repo, and still, they work as git repos so they are versioned, forkable and usable from git.
Pro GitHub Enterprise dows not render just markdown
GitHub does not render just markdown, it also renders geojson files, 3D models and csv files.
Pro GitHub has the ability to edit code right on the web page
With GitHub Enterprise edits to code files and to files in general can be made inline right on the web page UI.
Pro 45-day trial available
There is an option to test GitHub Enterprise for free for 45 days.
Pro Light-weight
Easy to install and setup. Can run on a VPS with 1 core CPU and 256MB RAM.
Pro Open source and maintained by community
Unlike Gogs, which is maintained primarily by its creator.
Pro Intuitive interface
Easy to navigate around and feels very natural in general.
Pro Non-memory consuming
Just like Gogs, but with new features and fixed bugs. Unlike GitLab which is enormous.
Pro Wiki and issues
Like GitHub, a wiki and issues (bugtracking) can be added to a repository.
Pro Fast pace of development
New features, constantly updated.
Pro Like Gogs but with faster bug fixes
If you love Gogs but were frustrated with the long wait for bugs to be fixed, this is for you.
Pro Most common platforms
Versions available for Linux, Mac and Windows. This is possible because Gitea is developed in the Go language which makes it compact and fast too. Only one executable is needed.
Pro Easy install with MariaDB back-end
No problems getting to work with MariaDB.
Pro Simple to install/written in GO
Pro Package Registry
Supports NuGet, npm, Cargo, Composer, Maven, RubyGems etc.
To work with the NuGet package registry, you can use command-line interface tools as well as NuGet features in various IDEs like Visual Studio.
Pro Runs perfect on a Raspberry Pi 3
Thanks to its light-weight and simple integration.
Pro Customizable Templates
All templates can be overridden.
Pro Focus only on key features
And if you want extra features, you can use web hooks.
Cons
Con Proprietary
If being proprietary in general is not bad enough, it's owned by Microsoft.
Con Can't natively manage large files and binaries (yet)
Max file size limited to 100MB. Git Large File Storage (GLFS) is in the works, but not ready yet. No other native options for large file/binary management.
Con No Continuous Integration packaged into the software
You'll have to set up Jenkins or pay for CircleCI, Travis, etc. in order to get CI running alongside GitHub Enterprise.
Con Update cycle lags behind public github
This is intentional, could be seen as advantageous.