RTFM: Technical Knowledge Base
A WordPress blog for failure patterns from operations and security, with its own theme in the design of disisto.de, articles in Markdown, login through Keycloak and a frontend that loads content only from its own server.
Since
2025
Scope
Theme, plugins, login and operations
Technologies
The Challenge
Fixes for operational problems otherwise end up in notes, tickets or chat histories and cannot be found the next time. A public knowledge base has to be as hardened as the systems it writes about, and must not hand its readers over to third parties.
The Solution
WordPress as the editorial system, but with its own theme, its own plugins and delivery that knows only its own server. Articles are written in Markdown, sign-in goes through the central Keycloak, and nginx sets a separate Content Security Policy for each area.
Structure
Own theme
Colours, gradients and components follow disisto.de. Light and dark can be switched, and the home page shows topics, popular articles and a search. Rotating lines in the header are maintained by category in a plugin of its own.
Writing in Markdown
Articles are written in Markdown instead of the block editor, with tables, code blocks and inline code. Failure patterns can be reproduced precisely with log lines, commands and timestamps.
Hardened delivery
nginx in front of PHP-FPM, WordPress objects in a Redis cache. The frontend allows scripts and styles only from its own server, uploads are served without executable content, and PHP reveals neither its version nor the default session name.
Sign-in through Keycloak
Editors sign in to the central Keycloak via OpenID Connect, using the self-developed Simple OIDC SSO plugin. User accounts are synchronised at sign-in, so no separate WordPress password is needed day to day.
Topics
Security, Linux and system administration, networking, Docker and containers, monitoring and observability, audio, and AI and development tools. Every article starts from a concrete failure and ends with a solution that can be followed step by step.
Operations
rtfm runs in its own Docker containers for WordPress, database, cache and nginx and is reachable only through the upstream reverse proxy. Images are built with the package state of the build day, and changes to theme and configuration are versioned in Git.
Privacy
The pages load nothing from third parties. Analytics are measured server-side by self-hosted Matomo and only after consent; anyone who allows only the essentials is not counted.
Results
A knowledge base that follows the rules it writes about: hardened, without dependence on outside services and with a sign-in tied into the rest of the infrastructure.
Gallery
Screenshots of rtfm.disisto.de.