11 Nov 2014
big surprise - new design!
I was already going through the interwebs for a few weeks, until I found some promising themes I wanted to try out on jekyllthemes.org.
trying hard again
In the last 5 days I went full jekyll mode. I switched to so many themes on my development environment, that I can hardly remember a single one of them.
But what caught my eye was scribble. I find it:
That’s about it. I’m easy to impress, I know. A few of my friends like it, others don’t. But what matters is my own opinion. And I like it a lot.
systemctl stop nginx
Oops. Let’s look at a few more details.
I’ve only got one cluster with two really cheap (5$) Digitalocean nodes deployed on it. It may seem not that much, but the cool thing is, that at the moment it’s more than enough.
On the other side, I’ve got way to many docker instances.
Yes, you saw right. 9 docker instances deployed on two 1CPU/500MB nodes. It gets kinda interesting to see how the services are connected with each other.
It took me way more time than I intended to draw this. So please, at least look at it for a few seconds.
Every connection between the services is accomplished with the docker linking technology. eyenx-ch-rp, the nginx reversproxy, is linked with the two loadbalancers eyen-ch-lb and eyenx-ch-dev-lb and these services are linked with their respective jekyll backends. For the loadbalancers I’m using the haproxy docker image provided by tutum as described in my previous post.
Personally I think that 4 containers in the production eyenx-ch-jekyll service might be a little overkill. But I’m just playing around with the tutum scaling capabilities.
When creating the jekyll services, I wanted them to have the sequential deployment option active. Sadly, upon finishing the service creation process, I saw the missing ON flag in the eyenx-ch-jekyll service details.
A few minutes later I tried again and took some screenshots for the purpose to contact the tutum support team. This was their response:
I gratefullly denied their kind offer. It just was nice to know they were already working on the fix.
This might not be a mistery. Anyway, I’ll show you my Dockerfiles on which I worked so hard (~10 minutes).
You may ask yourself why my start command is
git pull;jekyll serve.
I update the git repository under
/src every time the container starts. This gives me the possibility to update my static generated homepage without actually having to redeploy the whole service. I can achieve an update with absolutely no downtime with this simple for loop:
Finally let’s take a look at the eyenx-ch-rp Dockerfile.