While I don't have as many mishaps (yet!) to keep posting longer texts - I'd like to keep my profile alive and still share some experiences.
Even shorter and not as meticulous or informative - so here goes first issue of DevOpsWay Mini 🎉🎊
As for the topic - Vagrant - how to keep learning and not keep installing VMs
For those who don't know, Vagrant is a great tool that helps configure and provision Virtual Machines repeatedly.
Remember clicking through VirtualBox and installing OS? Remember how you wanted to take a break just after setting it up? Yea, me too.
Vagrant takes all of that away with a simple Vagrantfile called Vagrantfile (duh!) and command vagrant up... and command vagrant ssh.
In short, it contains all information needed to run the VM - like Operating System (called a box), specifying how much RAM and CPU cores it will have.
Additionally, we can provide information in provisioning section which amounts to Vagrant doing the job of Ansible and Terraform - but on local VM - or at least that's my understanding as of now.
The biggest takeaway is that you can create R&D labs in a few moments.
This is a great thing that has motivated me to actually try doing some network based stuff as I don't need to push anything to a server, nor pay for it, while still needing some network configuration.
My detour for this one was creating a simple godot "game" with headless server on a vagrant Linux VM connecting from a Windows Client!
(Also big shoutout to shared folders)
Pardon my polish text in the application and errors in the server CLI 😅
See you next time!
Top comments (0)