Interested in running DokuWiki on your website? Learn all about it and find out the best hosts for it here.
What Is DokuWiki?
DokuWiki is an Open Source wiki system geared toward documentation. It uses plain text files to store information, and has a focus on ease of use.
What Is a Wiki?
A wiki is a content-driven website that allows its users to update the content of any page. A wiki is powered by wiki software that manages user access, revision history, menus, and rendering (along with other typical website features).
Wiki User Privileges
While different users may have different privileges, and thus not every user may be able to edit any page, the concept of a wiki site is that there is a low level of permission needed to begin contributing.
Wiki systems assume that every user might become a contributor. To that end, one of the key characteristics of wiki systems is that they do not have a typical "back-end".
Editing and administrative functions tend to be available from the same public-facing user interface that displays content. This is unusual for most first-time wiki administrators and takes some getting used to.
Examples of Wiki Sites
Wiki sites are popular online. The premier example of a wiki is the encyclopedia site Wikipedia. Below is a list of popular Wiki sites:
Why Use Wiki?
As opposed to other forms of content management (such as a blog), a wiki is most appropriate when the knowledge you wish to collect and share is widely distributed.
It is especially appropriate if the consumers and producers of information will be part of the same peer group. In this case, a wiki allows members of the group to contribute their own knowledge, and then benefit from the knowledge contributed by other members of the same community.
DokuWiki is an Open Source wiki system built on PHP that allows you to easily launch a wiki site of your own. It places a strong development emphasis on being easy to use, which makes it an especially good choice for a non-technical contributor community. For this reason, many companies use DokuWiki for their corporate knowledge base.
DokuWiki has a number of competitors including MediaWiki and TikiWiki.
Here are a number of common features among Wiki sites:
- No Database Used
- Content stored in .txt format
- Simple syntax
- Highlighted diff comparison
- Embedded Images and Other Content
- Customizable Interwiki links
- Section Editing
- Automatic table of contents
- Page Locking
- Internationalization and Localization
Content Stored in .Txt Format
The most distinguishing feature of DokuWiki is that all the content is stored in plain text (.txt) files. It does not use a database, unlike almost all other wiki and content management systems.
No Database Used
This lack of a database makes the software easier to install, easier to configure, easier to back up, easier to restore after a failure, and easier to move.
It lowers the technical requirements for hosting, which makes it less expensive to run and available for a wider variety of hosting situations.
Most wiki systems use a somewhat complicated markup syntax for editing page content, requiring contributors to learn a set of unusual tags and typing conventions. DokuWiki's syntax is much simpler.
Additionally, DokuWiki provides, by way of plugins, support for alternative editing syntaxes, such as markdown.
Highlighted Diff Comparison
DokuWiki allows you to view versions of a page side-by-side, highlighting changes from one version to the next.
Embedded Images and Other Media
A page on the wiki can contain more than text. The editing screen provides an easy way to upload images, videos, sound files, and other media to the wiki, which can be placed on the page with simple embed tags.
Customizable Interwiki Links
This feature allows users to easily link to other commonly referenced sites, such as Wikipedia or Google, as well as to other pages on the same wiki. The feature is configurable, so you can allow easy-linking to any site your wiki community needs.
Users can open and edit a small portion of a page without having to navigate the entire article.
Automatic Table of Contents
Section headers in an article are automatically translated into a table of contents at the top of the page.
Moderators can prevent a page from being edited, or restrict access to only certain classes of users. This is especially important in a conflict over page content, or in the case of vandalism.
The system periodically autosaves while a page is open for editing, so progress is never lost.
DokuWiki supports a number of anti-spam measures, including read-only pages, granular control over page access, black-listing, email obfuscation, and nofollow links.
Internationalization and Localization
DokuWiki provides UI and editing support for over 50 languages. Additionally, multiple translations of a page can be created and toggled by the user.
DokuWiki has full support for templates to customize the site's look and plugins to customize its behavior. Over 80 templates and over 900 plugins are already available, and you can write your own as well.
DokuWiki Hosting Requirements
DokuWiki will run on almost any web server, as long as it has PHP 5.2 or later. There are very few hosts that won't install PHP on their servers as the default programming language.
|Web Server||Most hosts use Apache but many others including Microsoft IIS, Litespeed, Lighttpd, Nginx, and Abyss are known to work.|
|PHP||Must support PHP.|
|Web Browser||Any modern web browser|
The simplest and preferable option is to use a script installer. Most hosts will provide you with a control panel. Almost all control panels come with some sort of script installer that lets you install a wide variety of open source applications in just a few clicks.
DokuWiki is one of the most widely supported Wiki applications included in these installers. If DokuWiki is not available in a one-click installer, you can still use it, but you'll have to install it yourself.
You have 2 main options to do this:
- If you have root access to your server, you can install DokuWiki using a Docker image.
- If you do not have root access, download the DokuWiki files into any local directory before editing the configuration settings and transfering the files to your web server and running the installation script included.
Points to Remember
There are a number of features that you should look out for when purchasing DokuWiki hosting.
Here are some of the most important things to remember:
Find The Best DokuWiki Hosting For You
My Top 3 DokuWiki Hosts
There are a lot of hosts you can use DokuWiki with. That can make choosing very hard. So to help you out, I'm presenting what I think are the best three hosts for DokuWiki.
LiquidWeb DokuWiki Hosting via Whoishostingthis.com
If you're creating a serious Wiki, your server will have to support high traffic and bandwidth. Liquid Web offers some of the best high-performance servers and web hosting services possible. Most plans include a free copy of cPanel or Plesk, with an auto installer to install DokuWiki.
You also get root access to your server, so you can always uninstall or edit it through SSH. Liquid Web is a rare host that offers a 100% uptime guarantee. Finally, Liquid Web has amazing 24/7 support that will go above and beyond to help you set up and run your site with no issues.
SiteGround DokuWiki Hosting via Whoishostingthis.com
Another option for DokuWiki hosting that's a little more affordable is SiteGround. They offer cheap shared hosting, which is perfect when you're just starting out. You can then upgrade to their cloud or dedicated hosting packages if you need to support more traffic.
All servers come with free SSL and SSD, which helps your site run faster and more secure than it would without. You also get 24/7 support, and SiteGround has a fairly in-depth knowledge base.
iPage DokuWiki Hosting via Whoishostingthis.com
Finally, if budget is your main concern, and you're planning on creating a low traffic Wiki, iPage is a good option. iPage is a very simple host that only offers incredibly cheap shared hosting plans that will support a low traffic DokuWiki just fine.
You'll find one-click installers in your account's control panel for many popular applications, including DokuWiki. Just be cautious about going with iPage if you think your Wiki will get a lot more popular, as you'll have to migrate to another host at that point.
Here's What Your DokuWiki Hosting Needs To Offer
DokuWiki is an program for creating wiki applications. There are many reasons for creating specialized wikis, especially for development teams who want to document their work. And DokuWiki offers a particularly simple system for doing so. It is entirely text-based -- it uses no database backend. Still, it is quite powerful and uses a MediaWiki-like syntax. DokuWiki is often available through one-click installs. Check out SiteGround for DokuWiki hosting.
DokuWiki Hosting Frequently Asked Questions
Can DokuWiki be used for commercial websites?
Yes. DokuWiki is licensed under the GNU General Public License (GPL), meaning anyone can get the software and source code, use the software in any means they like, and change the source code in any way.
However, users must agree to the following terms:
This software comes with no guarantees, if you choose to redistribute the software you must do so under the terms of the GPL, meaning you redistribute the full source code with your changes, and you may not take credit for writing the full software.
As long as you agree to those terms, DokuWiki is free to use for whatever you like.
Does this have to be run on any specific server type or OS?
No. DokuWiki should work on any server running PHP 5.2 or later, whether Linux-based, Windows-based or other. There are OS-specific installation instructions available on the DokuWiki website for a large number of OS and server types.
What type of support is available?
There are a variety of free, community-based support options available, including a mailing list for development questions, a public forum for questions about usage and installation, and an IRC channel for smaller questions.
There are also a large number of resources already available on the DokuWiki website to assist you.
For those with the resources to pay for support, there are a number of professional support servers available from other companies. You can find a short list of those on their website, or using a quick Google search.
How can I get new features added if I’m not able to hire a programmer?
If you have a specific need, but do not want to or cannot afford to hire a programmer, DokuWiki offers a unique Bounty program, which is designed to encourage continued development.
Companies or individuals can set a “bounty” for a change or enhancement they would like to see, and set a price they are willing to offer for that change. If it’s a popular suggestion, other groups can also offer funds to the project.
Although it’s not guaranteed that a bounty will be taken up, it can be an effective way of getting changes made without having to contribute much in the way of capital.
Can I include HTML code into a DokuWiki page?
Yes. While DokuWiki pages are saved as simple text files, it is possible to embed HTML code to include enhanced formatting features.
To do so, you need to adjust the htmlock config settings and enclose all of the HTML content with HTML tags. Specific instructions are available on the DokuWiki website.
How do I create a backup of my DokuWiki site?
It couldn’t be easier to create a backup of your site. Since DokuWiki does not use a database, all you have to do is copy the files in your DokuWiki directory, just like you would copy a folder on your computer.
There are a number of backup plugins available to automate the process, so you don’t have to worry about ever losing data.
Can I set up notification for page changes or additions?
There are a number of options available for receiving notification for page changes.
You can set up one email address to receive global notification for every change made to your site. This email would typically go to you or your developer, but it could also be routed to a mailing list for additional recipients.
You can also enable the subscription server, so users can select to receive email notifications for changes to specific pages.
Or users can subscribe to your Wiki’s XML feed.
Can DokuWiki access information stored in a database?
Yes. DokuWiki includes built-in support for accessing authentication information from a database, and there are plugins available to add other database content, such including structured data from an SQLite database.
Can I require approval before page changes are published?
By default, DokuWiki does not allow you to set restrictions on content changes because it is designed to be an open publishing environment that allows quick changes to be made by any contributor.
However, the reality is there are some settings where that is just not a viable option, particularly in a corporate environment.
If approval is necessary before publishing new or altered content on your wiki site, you can install the Publish-plugin to set approval rules for your pages.
I’m thinking about using a wiki for my company’s internal site. Is DokuWiki a good option?
Yes. Wikis are great for company collaboration since they offer a quick, easy solution for creating and sharing content across your company.
DokuWiki is a particularly reliable choice because it has a large support community, hundreds of plugins, and dozens of templates available to suit your particular needs.
DokuWiki can be used for process documentation, a knowledge base, team manuals, project workspaces, and even your company intranet.
Is there a login feature for users?
Yes. You can require your users to login in order to edit and/or view content on your wiki site.
How can I move my DokuWiki site from one server to another?
This should be a fairly simple process. Just copy the entire DokuWiki directory from your source server and paste it into your destination server.
Keep in mind, some features may be affected by the move. Your last modified dates may change after the copy, so to prevent this you can save the directory into a TGZ file and unpack it on the new server.
Other features, such as permissions, .htaccess, and your cache may need to be adjusted after the move to ensure everything is functioning the same as before.