Decking

Decking aims to simplify the creation, organsation and running of clusters of Docker containers in a way which is familiar to developers; by reading information from a decking.json package file on a project by project basis.

While Docker is fantastic, it lacks any way of associating valuable metadata with images or containers. A Dockerfile can’t enforce that it be built as a certain image name. More importantly, an image can’t enforce that it be invoked with certain runtime values when it is used to create a container. Docker provides flexible, abstract building blocks. Decking transforms these building blocks into concrete implementations of services—and clusters of services—in a robust, repeatable, configuration-driven manner. It allows simple but powerful dependency modelling and takes all the hassle (and error) out of starting clusters of containers in the correct dependency order. It allows optional overrides to fine-tune cluster configuration on a per-environment basis.