Feature/configuration volumes

This combines what was discussed in PR #11 but adds two levels of configuration:

- Automatic Config
     - Just run it ... `sudo docker run -d nginx:1.x`
     - You get standard config as it runs today
- New Service Config
     - Added in a volume share `/nginx/conf.d` which allows new server sections to be added on a shared volume
     - The existing server config (aka, port 80) is still in play as are all the default settings in the "http" section
- Complete Control
     - Added another share under `/nginx/conf` which gives the host complete control
     - This allows setting anything wanted in "http" section, allows dynamic template generation of core config
     - Can be done in conjunction or independently of above share

> Note: By choosing `/nginx` as a base for configuration I have opted for a non-unix directory but in effect all I'm aiming to do is provide a compact and explanatory CLI for the host. Not sure if you'll agree with my thinking but I hope so ... I tend to fall in love with my own ideas.

> Last comment ... I'm sorry I couldn't have just let PR #11 run it's course but I needed something up and running immediately that met my needs. I'd love it if this could be brought back into the fold but if not then thank you for an excellent starting point.
Oh, also didn't mean to sneak this in there ... I just forgot to mention this change too. If this is a real bone of contention this is the least important part for me and I'd happily take it out. However, I may very well add a *bootstrapper* script to the entrypoint so that:

````bash
ENTRYPOINT ["bootstrapper"]
CMD ["start"]
````

This would allow the `start` param or no param to have the same effect of just running the nginx server but allows for other commands to be hung off of it too like possibly: `sudo docker run nginx version` which would report back a version number or `sudo docker run nginx ps` which would show the running processes. Do know of any examples of this style of setup? Seems intuitive but it has a few gotcha's in it too ... not least of which it would put **Nginx** back into daemon mode and the bootstrapper would need to preserve the running state.