When provisioning a GitHub Enterprise Server virtual machine, which storage design best supports performance and safe expansion of user data?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Root and data stay separate. Watch the data disk and grow it early — running out of space mid-day is a bad time to learn that lesson.
Full explanation below image
Full Explanation
GitHub Enterprise Server expects a root volume for the appliance OS and system components and a dedicated data volume for repositories, attachments, and other persistent user content. Separating volumes lets administrators grow user data without remaking the OS disk and reduces the risk that log or package growth on root starves Git storage. Expanding proactively after capacity monitoring is the operational standard. Combining everything on one thin volume and waiting until disk-full alerts invites outages. Hosting repositories only on an internet-mounted NFS share without a proper data disk violates supported design and security expectations. Memory-backed storage is ephemeral and cannot hold production Git data. Admins should plan IOPS, snapshot, and backup coverage around the data volume specifically.