Running Vagrant with Docker provider without password prompts on Fedora

When you run Vagrant with Docker provider you find out that you need to prepend every command with sudo since that’s what would you do with running Docker commands directly. But chances are you don’t want to do that. In that case it’s enough to make calls to Docker commands password-less. Vagrant would then be able to use Docker without password prompts as well. To do so you just need add yourself to docker group. Here is how to do it on Fedora 22.

Working with Bundler from your Ruby code

Have you ever wanted to use Bundler’s internals in your codebase? Here is how how to start by creating your Gemfile.lock, locking the environment and reading back the locked dependencies.

Patching gems for security vulnerabilities with gem-patch

gem-patch is a RubyGems plugin that helps you to patch gems. You can use it to apply security fixes or cherry-pick commits you want to apply to your .gem files. I use it to test whether the upstream commits containing vulnerability fixes apply cleanly on older gem releases so I can prepare fixed builds of those gems in Fedora. Here is how one can do that.

Running Kubernetes on Fedora with Vagrant

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.

Vagrant assistant for your DevAssistant

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.