Making this blog with Cloud Run

Until now In my first post on this blog, I explained how I created this blog. At the time, I was using: Hugo as a static site generator, that is a tool that turns Markdown into a pretty static website. AWS S3 to host the website itself. Docker to run Hugo and generate the website from my Markdown files. Since then, I joined Google and using Amazon’s services to host my personal blog didn’t seem very “corporate” :-) So, I had updated my setup like this:

Cleaning up Docker For Mac

Docker For Mac has really changed how I work: I now use it for all my linux-related developments. The integration is OS X is really well done and it’s really perfect for a development environment. The only problem is that Docker For Mac uses a file called Docker.qcow2 that takes more and more disk space as time passes (mine got to 20GB). Deleting images or containers does not decrease the size of this file.

Rancher Hands-On - part 2

Rancher Hands-On - part 1

Two weeks ago, I gave a presentation at the 42nd Docker Paris Meetup about Rancher. Rancher is a Docker orchestrator and, as such, a competitor of Docker Swarm and Kubernetes. However, it has some other features that make it very interesting and not incompatible with Swarm or Kubernetes. Here is the first part of the presentation: a general presentation of Rancher, a first demonstration: creating and scaling an Elasticsearch cluster in Rancher.

Making this blog

How is this blog made? As the first post on my new shiny blog, I found it fitting to explain how I make this blog, and how I host it. Spoiler alert: it involves all the latest trendy things in IT :-) Go, Hugo! Contemplating the prospect of hosting yet another Wordpress blog did not fill me with joy. Oh, the pain: choosing the right plugins, keeping it up-to-date or risking to be hacked… Wordpress is too complex for my needs and too time-consuming for me.