- Some updates (some delayed) on Engage 2020, Connections, my job and documentation as code
- Asciidoctor open links in new window
- DNUG Connections Day 2020
- Walkthrough: Vulnhub - DC: 3
- Walkthrough: Vulnhub - DC: 2
- Walkthrough: Vulnhub - DC: 1
- Walkthrough: Vulnhub - Djinn:1
- Talks 2020
- Automate hugo
- Walkthrough: Vulnhub - Me and My Girlfriend
During my talk at FrOSCon I wasn’t sure how to install Asciidoctor on Windows. So I tried on a Windows 10 VM. When you want to use Asciidoctor on a Windows desktop, you need to download the Rubyinstaller and install it. Now you can open a administrative command window and install with gem install asciidoctor. Let’s test with an easy document: test.adoc = Test Asciidoctor on Windows :icons: font == Admonition NOTE: Will this work? TIP: Convert with `asciidoctor test.adoc` Update I had a typo in the conversion command, you can still see it in the screenshot.
I often get SystemOut.log files from customers or friends to help them analyzing a problem. Often it is complicated to find the right server and application which generates the real error, because most WebSphere Applications (like IBM Connections or Sametime) are installed on different Application Servers and Nodes. So you need to open multiple large files in your editor, scroll each to the needed timestamps and check the lines before for possible error messages. Klaus Bild showed on several conferences and in his blog the functionality of ELK, so I thought about using ELK too. I started to build a virtual machine with ELK Stack (Elasticsearch, Logstash & Kibana) and imported my local logs and logs i got mailed.