Skip to main content
ドキュメントには� �繁に更新が� えられ、その都度公開されています。本ページの翻訳はま� 未完成な部分があることをご了承く� さい。最新の情� �については、英語のドキュメンテーションをご参照く� さい。本ページの翻訳に問題がある� �合はこちらまでご連絡く� さい。

このバージョンの GitHub Enterprise はこの日付をもって終了となりました: 2022-06-03. 重大なセキュリティの問題に対してであっても、パッチリリースは作成されません。 パフォーマンスの向上、セキュリティの改善、新機能のためには、最新バージョンのGitHub Enterpriseにアップグレードしてく� さい。 アップグレードに関する支援については、GitHub Enterprise supportに連絡してく� さい。

About GitHub Enterprise Server

GitHub Enterprise Server is a software development platform that you can host in a private environment.

GitHub Enterprise Serverについて

GitHub Enterprise Server is a self-hosted platform for software development within your enterprise. 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 can onboard and contribute seamlessly using familiar features and workflows.

GitHub Enterprise Server runs on your infrastructure and is governed by access and security controls that you define, such as firewalls, network policies, IAM, monitoring, and VPNs. GitHub Enterprise Server is suitable for use by enterprises that are subject to regulatory compliance, which helps to avoid issues that arise from software development platforms in the public cloud.

GitHub distributes GitHub Enterprise Server as a self-contained virtual appliance. After you provision a virtual machine and install the appliance, the instance runs a Linux operating system with a custom application stack. 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

詳細は「GitHub Enterprise Serverインスタンスをセットアップする」を参照してく� さい。

About releases and upgrades

GitHub Enterprise Server is constantly improving, with new functionality and bug fixes introduced through feature and patch releases. You are responsible for upgrades to your instance. For more information, see "GitHub Enterprise Server releases."

About administration

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 GitHub Enterprise Serverインスタンス. 詳しい情� �については、次の記事を参照してく� さい。

About optional features

You can configure optional features for GitHub Enterprise Server that improve the software development lifecycle for your enterprise.

機能説明詳細情� �
GitHub ActionsAutomate CI/CD and development workflows"About GitHub Actions for enterprises"
GitHub ConnectBenefit from the power of in limited waysGitHub Connectについて
GitHub Advanced SecurityImprove code security and qualityGitHub Advanced Security について
GitHub PackagesHost 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. 詳細は「High Availability の設定について」を参照してく� さい。
  • You can configure multiple active replicas to improve performance for developers who are geographically distant from your primary instance. 詳細は「Geo-replication について」を参照してく� さい。
  • Some enterprises with tens of thousands of developers may benefit from a cluster configuration that scales horizontally instead of vertically. 詳しい情� �については「クラスタリングについて」を参照してく� さい。

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バックアップユーティリティ. 詳しくは、" アプライアンスでのバックアップの設定。"を参照してく� さい。

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."

About documentation

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. 詳しい情� �については、「GitHub Enterprise Server のトライアルを設定する」を参照してく� さい。