Tackling Hugo Integration of Asciidoctor
Integrate Asciidoctor as everyone should expect While Hugo comes with Asciidoctor support, they are in reality several issues to account for at this time:
While basic rendering of asciidoc files works, we soon encounter problems ; the very first
Migrating From Jekyll to Hugo, deploying with Github Pages
Moving away form Jekyll. Import is easy, but tackling important details (conserve links to article, conserve comments, migrate some jekyll liquid template, theme tweaking deployment) has been challenging sometime.
Motivation When started this blog in 2010 I went like a lot other to Wordpress as this was the one of the most common and easy way to write and publish something, then I got pissed at Wordpress as it was a pain to maintain and to write code, not to mention the speed, it was bad, then Github announced Github Pages, this was a revelation : articles written in pure Markdown, no database or server to maintain, fast writing, fast page thanks to static files.
Gestion des dotfiles et des secrets avec chezmoi
Régulièrement il nous arrive d’avoir à re-configurer une nouvelle machine, avec notamment la re-configuration des fichiers du $HOME. Il y a plusieurs approches et outils, faire une simple archive, utiliser git pour le répertoire $HOME, utiliser des outils comme GNU stow, etc.
Managing dotfiles and secret with chezmoi
Every once in a while, you may need to bootstrap a new machine, and along with it to reconfigure home directory’s dot files. Various approaches already exist, using simple archive, git the home directory, gnu stow (symlinks), etc.
When Java's WatchService is not the right tool in a container
Boring code that should be written once and run everywhere Suppose the application you’re working on needs to monitor changes to a file and rely on Java’s WatchService introduced in Java 7.