keeb-zz

» meet-nick  time docker build -t keeb/meet-nick .
Uploading context 5.632 kB
Uploading context
Step 0 : from ubuntu:12.04
 ---> 8dbd9e392a96
Step 1 : maintainer Nick Stinemates <nick@stinemat.es>
 ---> Using cache
 ---> 688c24f5ff75
Step 2 : run apt-get update
 ---> Using cache

keeb-zz

» ~  docker run -u nobody -i -t ubuntu touch /tmp/test      
» ~  
» ~  docker ps -l
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
b360de514896        ubuntu:12.04        touch /tmp/test     5 seconds ago       Exit 0                                  distracted_torvalds   
» ~  docker commit b360de514896
73f2406aa2cd26d503992f9cfc8e28212bb0513f33094f74b34f4ed1e175c7bc
» ~  docker tag 73f2406aa2cd26d503992f9cfc8e28212bb0513f33094f74b34f4ed1e175c7bc nobody-test
» ~  docker run nobody-test ls -l /tmp
total 0

keeb-zz

Links - Spec

Links are a way of expressing a relationship between one container and another. When you link a container, you create a parent/child rlationship between the two. As a side effect links also allow you to name containers and reference them by name. Containers can be referenced by more than one name.

Initially links will be expressed with the environments of the children being injected into the parent accessible via namespaced environment variables:

####Examples

• REDIS_ENV_{key}={value}
• REDIS_PORT={value}

keeb-zz

I do most of my development on a remote server or on a local virtual instance. It just makes more sense, being able to work in a portable environment and pick up where I leave off lets me worry less about environment and more about the problem at hand.

One of the problems with using a technology like VirtualBox in combination with Docker is that Docker containers are truly portable and should expose a random port chosen by the host while VirtualBox port forwarding is static. You could, for every container, create a new port forwarding rule in your VirtualBox configuration, but that requires you change host configuration to be able to run your application. Not ideal and certainly not portable.

Enter hipache. Hipache is the best way to configure reverse proxies. In this example, hipache is the entrypoint for all web traffic on the host. Running hipache in a container just like any other service allows for ultimate flexibility.

Vagrantfile

Vagrant is a cool way of abstracting VM semantics and spin

keeb-zz

git config --global --add remote.origin.fetch "+refs/pull/*/head:refs/remotes/origin/pr/*"

keeb-zz

>>> a = ['a', 'b', 'c']
>>> a.extend(['d', 'e', 'f'])
>>> a
['a', 'b', 'c', 'd', 'e', 'f']

keeb-zz

import os 
folder = '/path/to/folder'
for the_file in os.listdir(folder):
    file_path = os.path.join(folder, the_file)
    try:
        if os.path.isfile(file_path):
            os.unlink(file_path)
    except Exception, e:
        print e