Skip to main content

Asciidoctor Windows

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`
windows adoc

Update
#

I had a typo in the conversion command, you can still see it in the screenshot. Sorry about that. You need to convert the source with asciidoctor test.adoc not .html!

To get the easy install into the documentation, I created a pull request at Github.

Christoph Stoettner
Author
Christoph Stoettner
I work at Vegard IT GmbH as a senior consultant, focusing on collaboration software, Kubernetes, security, and automation. I primarily work with HCL Connections, WebSphere Application Server, Kubernetes, Ansible, Terraform, and Linux. My daily work occasionally leads to technical talks and blog articles, which I share here more or less regularly.

Related

Froscon13

·102 words·1 min
Today I attended Froscon 13 in St. Augustin. Froscon is one or the biggest event around Opensource in Germany. Thanks again to organizers sponsors of this awesome event, it was a pleisure to be here and have the chance to give a talk. The slides for my session “Documentation with any editor” can be found at https://gitlab.com/stoeps/froscon18-presentation/blob/master/froscon13-documentationwithanyeditor.pdf.

New Blog Engine

·465 words·3 mins
I switched my blog to Hugo the last days. After nearly 12 years with WordPress, I needed something new. Why did I drop WordPress, one of the most used blog engines in the world? Most used means always most interesting for bad guys. Dynamic pages are slower and can contain more vulnerabilities than static pages (which Hugo generates). Hugo supports git, so I have version control in my posts and design. I can start a small web server locally and test the posts: hugo server -D and the most convenient thing: I can use VIM for editing.

Deleting temp and wstemp on Microsoft Windows Server

·267 words·2 mins
Since some versions of IBM Connections, it is mandatory to delete temp and wstemp of your Connections node after deployment or updates, or you end up with an old layout/design of Connections GUI. On a Windows Server System this can be a pain, because within temp/wstemp WebSphere Application Server creates a folder structure with nodename / application server name and so on. In must cases the delete ends with the message “path too long”.