Dokuwiki

Dokuwiki
Name	DokuWiki
Developer	Andreas Gohr
Released	2004
Programming language	PHP
License	GNU General Public License
Operating system	Cross-platform

Dokuwiki is a plain-text, file-based wiki engine focused on simplicity, readability, and maintainability. It has been developed and maintained by an active community since the early 2000s and is widely used by organizations, projects, and individuals for documentation and knowledge management. Its design emphasizes a low barrier to entry, extensible plugin architecture, and strong backward compatibility.

History

DokuWiki emerged in 2004 following influences from MediaWiki, TWiki, UseModWiki, PmWiki, and WikiWikiWeb, with technical lineage traceable through contributions from developers familiar with PHP projects and open-source communities such as SourceForge and GitHub. Early adoption involved projects associated with Debian, Fedora, Apache Software Foundation-hosted documentation, and corporate intranets used by organizations like NASA, European Space Agency, and Siemens. Over time, governance and development interactions reflected patterns seen in GNU Project, Free Software Foundation, Open Source Initiative, and coordination models used by Linux Foundation projects. Major releases incorporated standards discussed at venues such as IETF and implementations inspired by practices documented by W3C and contributors influenced by Linus Torvalds-style meritocracy. The ecosystem of themes and extensions grew akin to ecosystems around WordPress, Joomla!, and Drupal, and integration adapters mirrored connectors used by Jenkins, Trac, and Redmine.

Features

Dokuwiki's core provides editable pages stored as plain text with a lightweight markup similar to that used in Markdown-related projects and echoing syntax choices familiar to Emacs and Vim users. It includes built-in access control lists (ACLs) comparable to authentication schemes seen in LDAP, Active Directory, and single sign-on solutions like OAuth and SAML. Search capabilities resemble implementations from Lucene-inspired tools and are often extended by plugins integrating with Elasticsearch or Solr. Revision history and page diffs follow paradigms established in Subversion, Git, and Mercurial change tracking, enabling audit trails like those in Bugzilla and JIRA. Export functions support formats used by LaTeX, PDF, and office suites such as LibreOffice and Microsoft Office for technical writers working in environments including IEEE and ISO-compliant documentation workflows.

Architecture and Design

The architecture is deliberately file-based, avoiding relational databases used by MySQL, PostgreSQL, and SQLite in other wikis, which resonates with minimalist designs favored in BusyBox and Plan 9 philosophies. Implemented in PHP, it runs on web servers like Apache HTTP Server, Nginx, and Lighttpd and interoperates with operating systems ranging from Debian and Ubuntu to Red Hat Enterprise Linux, CentOS, FreeBSD, and Windows Server. Template and plugin systems follow modular patterns comparable to Eclipse plugins and GNOME extensions, while caching strategies echo approaches taken by Varnish and Memcached. File permissions and configuration mirror administration practices in OpenBSD and SELinux-aware deployments.

Installation and Configuration

Installation is typically a single-step deployment similar to web apps like WordPress and phpBB, requiring only a PHP runtime and writable filesystem like those managed with Ansible, Puppet, Chef, or SaltStack for automation. Administrators often integrate with continuous integration systems such as Jenkins, Travis CI, and GitLab CI/CD for deployment pipelines. Configuration files are edited directly or managed via version control systems like GitHub, GitLab, Bitbucket, and Mercurial repositories. Backups are handled in manners similar to strategies recommended by rsync, BorgBackup, and Duplicity users, and monitored using tools like Nagios, Zabbix, and Prometheus.

Plugins and Templates

A rich plugin ecosystem parallels the extension landscapes of Firefox and Chrome where contributors from communities around Stack Overflow and Reddit publish add-ons. Popular integrations include connectors for LDAP, OAuth, SAML, Jenkins, Confluence, Jira, GitHub, Bitbucket, GitLab, Docker, and Kubernetes. Templates and skins are created by designers influenced by Bootstrap, Foundation, and Material Design guidelines, with packaging and distribution patterns similar to repositories run by npm, Composer, and Packagist.

Security and Maintenance

Security practices recommended for deployments align with guidance from OWASP, CIS, and advisories circulated via CERT and US-CERT. Administrators apply patches and updates much like maintainers of OpenSSL, Apache Tomcat, and PHP itself, and integrate monitoring with Splunk, ELK Stack, and Graylog for log analysis. Role-based ACLs are often tied to identity providers such as Azure Active Directory, Okta, and OneLogin, and operators follow incident response templates used by SANS Institute and compliance frameworks from NIST and ISO.

Adoption and Use Cases

Dokuwiki is used across academic institutions like MIT, Stanford University, and University of Cambridge; government agencies including European Commission initiatives and municipal IT departments; and corporations from IBM-sized enterprises to startups incubated by Y Combinator. Common use cases include internal knowledge bases, project documentation for teams using Agile and Scrum methodologies, technical manuals for hardware vendors collaborating with Intel, AMD, and ARM Holdings, and community-driven wikis associated with OpenStreetMap, Wikimedia Foundation-adjacent projects, and software communities around Kubernetes, Docker, Ansible, and Terraform.

Category:Wiki software