Apache Tomcat is well known to be a lightweight and fast web container. This makes it a perfect fit for running your Java based web applications. Doing just that and playing around with Docker Tutum and Digitalocean I discovered that starting up a Docker Container, which would take <25s locally took over 2 minutes when being deployed on a Digitalocean server. Digging through the logs, the following line cought my attention: INFO: Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [199,620] milliseconds.
Docker images are the way to distribute preconfigured, rebuildable containers. This can for example be used to: persist the runtime configuration for a project in the SCM system of your choice and exchange configurations between team members get new team members up and running in minutes instead of days aleviate the burden of keeping a running dev environment up to date as long as the software is in production - even if the backlog is empty …and many more To create a docker image you basically have two options: start a container, customize the environment to your liking and finally package the container as a reusable image build an image by means of a Dockerfile If you plan on reusing and distributing your image it is always recommended to use a Dockerfile to describe the resulting environment.
Hugo is a static CMS system. In this case static means, that all the content is rendered to static html markup. So there is no need for anything else than a HTTP server to run your site. This makes the whole thing a lot less complicated as well as a lot more secure. The content for a site which is generated by Hugo is generally edited in markdown files. This gives you the possibility to edit everything disconnected as well as choose the tools you like for your writing Installation If you are running on a mac and are using homebrew (which you probably should anyway) just brew install hugo.
f1r5t!!!!111!1!elf!111! Lets get this party started!