Once GitHub Enterprise is up and running, you can configure the appliance to suit your organization's needs.
Use the Management Console to set up and configure GitHub, schedule maintenance windows, troubleshoot issues, and manage your license.
SSH access allows you to run the GitHub Enterprise command line utilities and is useful for troubleshooting, running backups, and configuring replication.
Some standard maintenance procedures, such as upgrading your GitHub Enterprise instance or restoring backups, require that the GitHub Enterprise instance be taken offline for normal use.
As part of a disaster recovery plan, you can protect production data on your GitHub Enterprise instance by configuring automated backups.
In private mode, GitHub Enterprise requires every user to sign in to access the installation.
You can set the default visibility for all new repositories created via the web interface on your GitHub Enterprise appliance to be private or public.
You can require people to resolve merge conflicts locally by disabling the merge conflict editor on GitHub Enterprise for pull requests where the base branch and the head branch are in different repositories.
You can disable Git SSH access to certain or all repositories on a GitHub Enterprise appliance to prevent people from using Git over SSH to access repositories.
You can enable or disable GitHub Pages on your instance. You can also choose to make GitHub Pages sites publicly accessible.
You can set rate limits for GitHub Enterprise using the Management Console.
If you run into SSL issues with your appliance, you can take actions to resolve them.
GitHub Enterprise automatically synchronizes its clock by connecting to NTP servers. You can set the NTP servers that are used to synchronize the clock, or you can use the default NTP servers.