kosyfrances

KVM in runc

Running a KVM virtual machine inside a runc contianer.

Requirements

• A host which can run KVM virtual machines using Vagrant.

Setting up a test VM

kosyfrances

If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.

To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.

1. Clone some repo (you've probably already done this step).

   git clone git@github...some-repo.git

kosyfrances

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console