GitHub Enterprise Server Administration - Best practices from GitHub Support

Every day, the GitHub Enterprise Support team assists GitHub Enterprise Server administrators in managing, securing, and supporting the most critical and central hub of their organization’s development lifecycle. We’ve been keeping track of best practices for GitHub Enterprise Server Administrators that you can apply in your environment.

Overprovision hardware for growth

Test / Staging environments

High Availability and Disaster Recovery (Backups)

  • Configuring at least one High Avalaiblity Replica is advised for redundancy and ease of recovery in the event of a primary appliance failure.
  • GitHub Enterprise Backup Utilities should be configured and backups scheduled to run regularly against your GitHub Enterprise Servers. Testing restores to a staging or test environment is also equally important.
  • Placing replicas and GitHub Enterprise Backup Utilities hosts in different regions or datacenters from the primary appliance can help to ensure geographic redundancy.

Implement policies for rate limiting and abuse

  • API and Git rate limiting is only effective if you also set enforceable, policy-backed limits. Exceptions to your rate-limiting policy should be rare and used for specific integrations and service accounts that are outliers to your normal user API usage.
  • Use log forwarding and collectd metrics forwarding to spot increases in request rates, bad actors, and patterns.
  • CLI usage reporting tools such as ghe-governor-summary, ghe-btop, should be regularly reviewed for outlying or abusive behaviors.
  • Suspend bad actors, or block them at a network or firewall level.

Be a good CI or API citizen

  • Use webhooks rather than cron-style polling
  • If Cron-style polling has to be done, spread out and skew the fetches to reduce parallel requests.
  • Utilize conditional requests with the GitHub API, and ensure that CI plugins are up to date, with caching features enabled as well.
  • Build artifacts, logs, or even data backups should not be stored in git (especially in refs/heads). Git is not designed to be a database. Use Git LFS when dealing with large files to keep Git performing great.
  • Frequent automated pushes can be even more impactful on overall performance than frequent fetches. Limit usage of cron style pushes, and batch multiple commits into a single push where possible if automating pushes on a schedule.

Join the conversation!

Now you have some best practices to manage your GitHub Enterprise Server environment and tips to make it more secure and reliable. At the end of the day, maintaining a healthy and reliable environment is up to how you and your team manage it. What are some of your go-to practices? Please feel free to share in the comments below!


My name is Katilya Sharee Strickland I’m trying to start my business accounts with my business and online streaming services store and services my business brand name is queenkisseslacefrontwigs and I’m also a promoter writer and singer and creator and decorator and also developer and the owner of my personal and family services store owner as well in will like to get resources again cause of the last few times my merchandise did get sent to me or my address please contact me asap

Hi there @QueenKatilya7 and welcome to the Community Forum :wave: For account-specific queries like this I recommend reaching out to your account manager or contacting Support.