About GitHub Enterprise Server
GitHub Enterprise Server 是企业内软件开发的一个自承载平台。 Your team can use GitHub Enterprise Server to build and ship software using Git version control, powerful APIs, productivity and collaboration tools, and integrations. Developers familiar with GitHub.com can onboard and contribute seamlessly using familiar features and workflows. 若要详细了解企业如何使用 GitHub 的产品来支持自身的软件开发生命周期，请参阅“关于 GitHub for enterprises”。
GitHub Enterprise Server 在基础结构上运行，受� 定义的访问和安全控制措施（例如防火墙、网络策略、IAM、监视和 VPN）约束。 GitHub Enterprise Server 适用于受法规合规性约束的企业，它有助于避免公有云中的软件开发平台引发的问题。
GitHub 将 GitHub Enterprise Server 作为独立虚拟设备分发。 当� 预配虚拟机并安装设备后，该实例运行带自定义应用程序� �� �的 Linux 操作系统。 For more information, see "System overview."
You can choose to deploy GitHub Enterprise Server on premises, or to a supported cloud environment.
Supported environments for deployment
You can deploy GitHub Enterprise Server to a virtualization hypervisor within your on-premises datacenter, or to a public cloud service.
GitHub supports the following virtualization hypervisors for on-premises deployment.
- Microsoft Hyper-V
- OpenStack KVM
- VMware ESXi
GitHub supports the following services for cloud deployment.
- Amazon Web Services (AWS)
- Google Cloud Platform (GCP)
- Microsoft Azure
For more information, see "Setting up a GitHub Enterprise Server instance."
About releases and upgrades
GitHub Enterprise Server 在不断改进，通过 功能和补丁 引入新功能和漏洞补丁。 You are responsible for upgrades to your instance. For more information, see "GitHub Enterprise Server releases."
You can configure and monitor GitHub Enterprise Server via browser, administrative SSH access, and REST or GraphQL APIs. GitHub has found that people with Linux administration experience are more successful with the deployment and maintainance of GitHub Enterprise Server.
You can give certain employees administrative access to GitHub Enterprise Server, so they can set up external authentication, configure the instance to meet developer needs, and monitor the instance's activity and performance. To ensure compliance with business rules or regulatory restrictions, administrators can configure policies that control how people use your GitHub Enterprise Server instance. For more information, see the following articles.
- "About authentication for your enterprise"
- "Configuring your enterprise"
- "About the GitHub Enterprise API"
- "Monitoring your appliance"
- "Monitoring activity in your enterprise"
- "About enterprise policies"
About optional features
You can configure optional features for GitHub Enterprise Server that improve the software development lifecycle for your enterprise.
|GitHub Actions||Automate CI/CD and development workflows||"About GitHub Actions for enterprises"|
|GitHub Connect||Benefit from the power of GitHub.com in limited ways||"About GitHub Connect"|
|GitHub Advanced Security||Improve code security and quality||"About GitHub Advanced Security"|
|GitHub Packages||Host software packages for your enterprise||"Introduction to GitHub Packages"|
About deployment topologies
By default, GitHub Enterprise Server runs as a standalone instance. You can increase the reliability and performance of GitHub Enterprise Server by using a different topology for your deployment.
- To mitigate the impact of system or network failures, you can deploy a passive replica instance. During an outage that affects your primary instance, you can manually fail over to the replica instance. For more information, see "About high availability configuration."
- You can configure multiple active replicas to improve performance for developers who are geographically distant from your primary instance. For more information, see "About geo-replication."
- Some enterprises with tens of thousands of developers may benefit from a cluster configuration that scales horizontally instead of vertically. For more information, see "About clustering."
About backups and disaster recovery
To safeguard against data loss or service disruptions for your developers, GitHub strongly recommends that you establish a plan for disaster recovery. You can back up your instance's configuration and user data by deploying and configuring a Linux or Unix host system with GitHub Enterprise Server Backup Utilities. For more information, see "Configuring backups on your appliance."
Additionally, you can configure a passive replica instance to fail over to in the event of a system or network failure. For more information, see "About deployment topologies."
Documentation for both administrators and users of GitHub Enterprise Server is available on this site, GitHub Docs.
Different versions of GitHub Enterprise Server are reflected separately in the documentation on GitHub Docs. For more information, see "About versions of GitHub Docs."
Trying GitHub Enterprise Server
You can sign up for a free, 45-day trial of GitHub Enterprise Server. For more information, see "Setting up a trial of GitHub Enterprise Server."
- "Getting started with GitHub Enterprise Server"
- "About GitHub 支持"
- GitHub public roadmap in the