123 points

der.hans is a technology and entrepreneurial veteran. As a volunteer der.hans endeavors to help build community through user group and conference leadership.

He is co-chair of Open Source Career Day (OSCD) at Southern California Linux Expo (SCaLE) and chair of the Finance and Partnership committees for SeaGL.

He presents and gives career counseling sessions at large community-led conferences (SCaLE, SeaGL, Tux-Tage, Kielux, GeekBeacon Fest, FOSSASIA, LCA, LFNW, Tübix, OLF ) and many local groups. He is chairman of the Phoenix Linux User Group (PLUG) and founder of the Free Software Stammtisch.

Work roles have included director of engineering, engineering manager, IS manager, system administrator, community college instructor, developer and DBA.

Currently he manages a team of database support engineers at Object Rocket, part of Rackspace Technology.

Find Hans on the Fediverse -

Authored Content

Authored Comments

Thanks for the Pandoc articles. I learned a few useful things.

In this article, I noticed a typo.

"originally written in LaTeX and rewrites it in Markdown"


Utku - Configuration Mangement Systems (CMS) such as puppet, ansible and chef are great and provide part of what I describe in the article. Professional environments should be using CMS or other reproducable, automated, scalable tools for deployment. In most cases a CMS does not track all files in /etc/, so I suggest keeping /etc/ in etckeeper on the CMS managed server in addition to the CMS.

I admit that might be a hard case to make in a virtualized environment, so consider the missing features and whether or not they matter for your environment.