)

~~~
dchuk
Thanks for the links!

------
shykes
That video of the project's activity over time is pretty awesome and almost
brought a tear to my eye :)
[https://www.youtube.com/watch?v=FCiS812oRU8](https://www.youtube.com/watch?v=FCiS812oRU8)
(link didn't work for me on iOS)

~~~
gabemart
It's a really impressive visualization. Does anyone know how it was made?

~~~
julien421
We used Gource:
[https://code.google.com/p/gource/](https://code.google.com/p/gource/)

~~~
nodesocket
On OS X you can install with:

    
    
        brew install gource

------
aus_
I work for a large financial company. At our shop, we are currently building
out an internal cloud infrastructure where we build on too of the OpenStack
API to provide users with self service deployment much like AWS.

In order to deploy to production, we mandate a process requiring users to have
an existing chef recipe before any production guest can be deployed. We also
restrict logins to existing production nodes unless there is an emergency.
(This attempts to keep configuration management entropy to a minimum.) all of
this works ok, but I think it could be better with Docker.

In a few weeks, I have a chance to present a new idea to senior executives.
I'd like to pitch Docker, at least as something to keep an eye on. Any
thoughts on what points I should drive home?

~~~
jschorr
Offhand, the major benefits for your use case seem to be:

\- Speed and Flexibility: Extremely quick turn around time from development to
production; Docker images usually start in under 10s and multiple images can
be run concurrently. If a user needs to update their running service(s), they
can even have multiple versions running at the same time behind something like
HAProxy (which itself could be in another Docker container), allowing real-
time migration.

\- If your users build their images and test them on their own machines, they
can then deploy the same images to your production machines with the knowledge
that (barring unusual circumstances) they will have the same exact 