Skip to content

Instantly share code, notes, and snippets.

View roelvanduijnhoven's full-sized avatar

Roel van Duijnhoven roelvanduijnhoven

View GitHub Profile
@chmanie
chmanie / bye-bye-vagrant.md
Last active August 29, 2015 14:16
Bye bye Vagrant

Bye, bye Vagrant

Setting up a small footprint development-environment with boot2docker and docker-compose

The idea of providing a dedicated, encapsulated development environment with is basically the same for all of your teams' members has been around for a while. For quite some time Vagrant seemed to be the state-of-the-art solution for such needs. In combination with puppet for example one could easily set up a fully working VM with all dependencies installed and set up. But Vagrant is kind of an monstrosity. There are so many things that could possibly go wrong while provisioning a Vagrant machine. Also, if you happen to have a lot of projects using Vagrant the VMs are probably using a lot of your precious SSDs disk space. The small containerized images build with Docker seemed to be an interesting alternative, but rather hard to maintain in the past.

Fear no more! docker-compose has you covered. But there a

@piscisaureus
piscisaureus / pr.md
Created August 13, 2012 16:12
Checkout github pull requests locally

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = git@github.com:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: