I’m recommending doing a GUI on the base system so it’s easy to install the guest images.ĭo a quick check to make sure your CPU supports KVM. Customize it to your liking, installing base packages, setting up users, passwords, vim profiles, etc. If you already have a hypervisor setup or want to do it differently, skip the Hypervisor Setup and Hypervisor Networking sections. Also there are annoyances like Windows 10 rebooting in the middle of the night, taking down all the hosted VMs in the process. I try to keep these VMs to a temporary basis because using a primary desktop/laptop will not have the always-on uptime, useful for any hosted service. On my main Windows desktop, there are usually a random collection of tinker machines… If you don’t have any spare hardware, your main desktop/laptop can work for a temporary solution. So I want to separate the machines to keep memory usage in strict control. Also I’ve noticed that Gitlab is a memory hog, even with one active user. The reason being is that Gitlab strongly discourages installing Gitlab and runners on the same OS.
One machine for Gitlab, and two for the runners. We are going to need three total VMs with 8GB total memory and maybe 128GB disk space. The hardware required is something that supports virtual machines.
Where do you store your code projects – Github? What about private projects…do you pay for private repos? You can have more control over your projects and even configure automated tests and builds – all using open source software! Fire up your spare hypervisor and read on to learn how to build your own dev project host! Read over my About page to see how I show commands/output and read the disclaimer. Posts here are mostly step-by-step guides on how to replicate something I have set up in the past.
0 kommentar(er)
