A markdown based wiki about Linux, Open Source, VoIP and other geeky stuff.
Sources of this site are available on Github.
You can't comment here but you can open an issue or submit a merge request on Github if something is incorrect or requires clarification.
Opinions expressed here represent my own and not those of my employer.
What I'm up to today
I'm a senior consultant at Red Hat, the Open Source company.
To learn more about our consulting service, check https://www.redhat.com/en/services/consulting.
What I have been up to in the past
For those who have been following me from the start, you've heard that I was really into Linux, Postfix, OpenVPN and Asterisk for some time, back when I was managing 5 Linux servers or so.
Then I changed jobs a couple of times and, and eventually managed more than 330 servers. In my last position before starting at Red Hat, I spent a lot of time automating, centralizing and orchestrating system administration and management with those tools:
On the personal level
My work environment
I work in a virtual machine running the latest Fedora with i3 tiling window manager.
The VM runs on top of a Red Hat Enterprise Linux host running libvirt.
I'm a die-hard shortcut keyboard user.
Why a wiki?
Story time. I started this website in June 2005 (but bought the domain in March of the same year). The idea was to save notes about my findings so I could look them up later. I figured that I would share them online so it would probably help someone else down the line.
It all started as a self-hosted Wordpress blog as
www.wains.be (changed to
blog.wains.be around September 2011). I had a lot of times on my hands and I was able to interact with my readers. On the busiest months I was getting 20000 visits a month. After a while, spam, bots and security issues became problematic, and the maintenance became a burden (files and database backup, PHP and security upgrades, dist-upgrades, etc.). I became kind of bored of maintaining or even publishing anything.
I needed something different. Something more automated and less cumbersome.
I wanted to publish things quickly, from anywhere in the world. I wanted to be able to write offline, and see my content pushed online almost automagically as I was getting a connection.
So here we are, July 2015, almost exactly 10 years later, the blog platform became a wiki platform. The (somewhat aging) content is still there and I hope you find useful stuff.
In 2015, it was running Wikitten.
In 2017 revision, I moved to Mkdocs as Wikitten didn't have a search engine and was not actively developed.
I write articles on my personal computer.
Markdown has some great advantages :
- stored as plain text on disk
- content is indexed making it easy to find content with Alfred/Spotlight/grep
- you can grep, sed, awk the hell out of them and bring corrections very quickly
- can be stored in a Git repository
This is my current publication workflow:
- I edit articles locally with Visual Studio Code (yes, it is an open source Microsoft product, and it is very good)
- I commit changes to my GitHub
- With an Alfred workflow, I connect to my VPS and do:
- a "git pull" to retrieve updates
- rebuild the doc (which is served as static files by the HTTP server)
- Article is online
I like building simple, powerful, resilient, secure and automated infrastructures. Preferably based on open tools and protocols. Privacy and security are a concern.
When I'm not busy at the computer, I travel, hike, ski, camp out and take photos.
If you want to contact me, just look me up.
Found an error on this site?
Open an issue on Github