Warning: The process for allocating new system resources varies by virtualization platform and resource type. You should always configure the monitoring and alerting of key system resources. For more information, see "Monitoring your GitHub Enterprise Server appliance."
As more users join your GitHub Enterprise Server instance, you may need to resize your storage volume. Refer to the documentation for your virtualization platform for information on resizing storage.
Note: Before resizing the user storage volume, put your instance in maintenance mode. For more information, see "Enabling and scheduling maintenance mode."
Note: If you enable GitHub Actions or GitHub Packages, your instance requires additional hardware resources. Minimum requirements for an instance with beta features enabled are bold in the following table. For more information, see "Beta features in GitHub Enterprise Server 2.22."
|User licenses||vCPUs||Memory||Attached storage||Root storage|
|Trial, demo, or 10 light users||2|
or 32 GB
or 150 GB
|10 to 3,000||4|
or 48 GB
or 300 GB
|3,000 to 5000||8|
|64 GB||500 GB||200 GB|
|5,000 to 8000||12|
|96 GB||750 GB||200 GB|
|8,000 to 10,000+||16|
or 160 GB
|1000 GB||200 GB|
You can sign up for beta features available in GitHub Enterprise Server 2.22 such as GitHub Actions, GitHub Packages, and code scanning. For more information, see the release notes for the 2.22 series on the GitHub Enterprise website.
If you enable beta features for GitHub Enterprise Server 2.22, your instance requires additional hardware resources. For more information, see "Minimum requirements".
- Resize the existing user volume disk using your virtualization platform's tools.
- SSH into your GitHub Enterprise Server instance.
$ ssh -p 122 admin@HOSTNAME
- Put the appliance in maintenance mode. For more information, see "Enabling and scheduling maintenance mode."
- Reboot the appliance to detect the new storage allocation.
- Run the
ghe-storage-extendcommand to expand the
- Set up a new GitHub Enterprise Server instance with a larger root disk using the same version as your current appliance. For more information, see "Setting up a GitHub Enterprise Server instance."
- Shut down the current appliance.
- Detach the data disk from the current appliance using your virtualization platform's tools.
- Attach the data disk to the new appliance with the larger root disk.
- Attach a new disk to your GitHub Enterprise Server appliance.
- Run the
partedcommand to format the disk:
$ sudo parted /dev/xvdg mklabel msdos $ sudo parted /dev/xvdg mkpart primary ext4 0% 50% $ sudo parted /dev/xvdg mkpart primary ext4 50% 100%
- Run the
ghe-upgradecommand to install a full, platform specific package to the newly partitioned disk. A universal hotpatch upgrade package, such as
github-enterprise-2.11.9.hpkg, will not work as expected.
$ ghe-upgrade PACKAGE-NAME.pkg -s -t /dev/xvdg1
- Shut down the appliance.
- In the hypervisor, remove the old root disk and attach the new root disk at the same location as the old root disk.
- Start the appliance.