It basically builds.
It basically works.
It has a problem; it's supposed to move everything into /config and then
symlink /etc/puppet to /config, but it just ends up deleting everything.
Dag, yo.
Much change!
No need for removing wget, not installed.
Directory permissions now sane at /data and
/data/{modules,manifests,environments}.
Work in progress: manual cert generation, fixed agent.
Pairs with itself, can apply configuration.

Now based on phusion/baseimage directly. Has its own Puppet Agent
script. Doesn't erase apt cache because this then requires users to run
apt-get update. Basically, it works. Provides also symlinks into the
production environment. More environment variables for configuration.
Basically, the only thing holding off on a 1.0.0 release is
documentation.
Require latest Puppet client on Vagrant box.
Environments work, but only with manual specifying.

In work for issue #6 (add --confdir and remove the other parameters),
I've discovered what seems to be a bug with Puppet Master and how it
does things.

With a Puppet Agent with --environment production, I _have to_ specify
--environmentpath on the Puppet Master in order for it to pick up the
changes and attempt to run them. Even though I'm specifying --confdir
and it _should_ pick up $confdir/environments for --environmentpath, it
doesn't and requires manually specifying it on the command line.

I'm about to test and verify that this is actually what is going on.
Environments working with base module path.

Providing by default the production environment. Everything is now
living in /data with proper permissions. I don't know if I like the
sticky bit and if its necessary but it's working. I also have a hanging
/data/manifests directory which I don't like.

Tested and working with local Puppet Agent.
Merge branch 'feature/issue6' into develop
Updating documentations.
Added as utilities the 'lxc' and 'tree' packages.
Now based on rfkrocktk/baseimage:1.0.0.

Closes issue #8.
Upgraded to baseimage 1.1.0.

Closes #11.
Preparing for NGINX+Passenger server.

Added NGINX and Passenger installation and configuration files.
Migrated key generation to init script.

We now generate Puppet Master keys on startup before anything else runs
in an init script in `/etc/my_init.d/`.
Successfully served over Passenger+NGINX.

The Puppet Master is now correctly working as served over NGINX and
Passenger. We dealt with header issues which were giving us 403s. Need a
better way of regenerating the Puppet config file which doesn't
overwrite every single time.
Reworked generation of Puppet config to be failsafe.

Now, we backup the default configuration on container build then copy
this over if it's not present on container start. We also create the
right directories, chown everything, and template generate the
puppet.conf file as before.