Do you always think twice before downloading software that comes in a tar or zip file? Me too, I like to manage my software in easy and straightforward manner and that’s why I repackaged Otto, Packer and Vault in RPM format. If you are running Fedora, CentOS or RHEL 6 you can now use my Copr repositories for the mentioned software from HashiCorp.
Fedora/CentOS RPMs for Otto project, Packer and Vault
Using OpenShift s2i Docker images to build Ruby application containers
Build your Ruby application’s Docker image in just one line of code without writing any Dockerfile! You only need source-to-image tool (s2i, formally sti) and Docker.
Debugging Vagrant with pry-byebug
What to do when running Vagrant with
--debug flag is not enough? As Vagrant is nothing else than a Ruby program, you can use famous
pry gem together with
pry-byebug to debug it. The only thing you need to do to use
pry from the Vagrant code base is to make sure it’s installed and available in the Vagrant environment.
Why Fedora needs a place for developers
I would like to share with you my own opinion on why I initially joined Petr Hráček in pursuing the idea of a portal for developers running Fedora and why I think that this project will help new and existing developers to take advantage of everything Fedora Workstation has to offer.
Writing a general multi-provider Vagrantfile
Vagrant is a great software that allows people to use various providers, provisioners, sync options, and more. But that often comes short if we write our project’s Vagrantfile just for default VirtualBox. Since I prefer to use libvirt provider and NFS I tend to write Vagrantfile that only support those (as they are just for myself). But lately I was writing a Vagrantfile for upcoming Fedora Developer Portal and wanted to support both Fedora users running our packages with libvirt as a default provider and everyone else as well.