I’m aiming to write something every day this month but in actuality, I write things most days — just not here. Usually it’s work and code so most people won’t find it all that interesting; at least it should provide me with some material to write about.
I mentioned my attempts at shaving vital grams off my bikepacking gear yesterday. Today, I’m going to write about applying the same principle to the development workflow that I’ve switched to this year, namely Docker.
For the uninitiated, Docker is a way of packing the code you write into self-contained units. These containers are built on top of a base operating system and these can vary greatly in size.
I’m currently building my own suite of custom containers, configured for exactly how I like to work, starting with PHP-FPM, nginx, Redis and Postgres along with Node for running Gulp build tasks and the ELK stack (Elasticsearch, Logstash, and Kibana).
I have yet to deploy Docker to production, let alone be approaching implementing any form of continuous deployment practice but ultimately smaller containers will lead to faster deployment times and tighter feedback loops which are all good things.