Kubernetes is a Container Cluster Manager from Google which basically means that Kubernetes is an orchestration of many services running on plenty of Docker containers. Google actually supports a several ways how to run Kubernetes and luckily Vagrant is one of them.
You have probably heard about Vagrant coming to Fedora and might have heard about DevAssistant too. DevAssistant can make your development easier by setting up your project’s basic structure, installing needed dependencies or tools. But if you wanted to use Vagrant for your project as well, you needed to install and configure it separately. Until now.
What do you usually do when releasing a new version of gems? Running test suite? Something more? I like to use my tool on tracking changes in RubyGems gem-compare as it gives me a little bit more confidence on what am I actually releasing. Here’s how I do it.
Since I package and maintain Vagrant and vagrant-libvirt for Fedora, I have a need to test new builds. But since I run just one version of Fedora and I don’t really feel like testing it directly on my host system, I actually use Vagrant to test Vagrant. In other words I run Vagrant with KVM and inside I download the new builds and run Vagrant with KVM again. This is possible because KVM supports nested virtualization. In fact I already wrote about setting that up with virt-manager. But today I show you how to do it using Vagrant itself.
As you probably know, you can use
eval() to evaluate Ruby code from Ruby. But evaluating things that come from the outside of the program like user inputs can be dangerous. Why they can be dangerous you ask?
eval() evaluates anything as we would program it ourselves. Basically anything can happen. That’s why it’s best to avoid
eval() for such inputs altogether. But we can evaluate Ruby in a safer manner too; with