So in our previous post Haproxy ssl termination for Jekyll we learned how to create a docker container capable of creating self-signed certificates or use previously created certificates to create our haproxy ssl termination to our backends, and always make sure our certificates were re-evaluated by haproxy on each change....
For this blog’s first post I described a simple start for people getting into Jekyll blogging by using docker and how to start a blog using a Jekyll docker based image with a ready to use theme.
So recently while working on some ansible automation, and in my testing container I realized I created by hand a symbolic link I could not remember. By hand I mean I did not automate the creation inside an ansible task.
Version 2.0.+ of Vagrant default hosts to 127.0.0.1 in /etc/hosts with docker provider
Ruby gems certificate checking solving giving out some troubles [The solution present on this post assumes using a unix system]