A practical DokuWiki home on Ubuntu
A personal wiki is useful when project notes, household records and half-finished ideas need one dependable home. DokuWiki on Ubuntu suits that role because it stores pages as readable files, keeps revision history and serves everything through a browser. It is less decorative than a cloud workspace, but that restraint helps information remain useful years later.
The platform can run on a spare laptop, a small server in Melbourne or Brisbane, a Raspberry Pi in a Perth home office, or a virtual machine used by a regional developer. There is no per-user licence fee or proprietary database to maintain. You decide who can read or edit pages, how attachments are stored, and whether access stops at the local network or reaches other devices.
Getting the first version running is straightforward; making it secure, searchable and pleasant to maintain is the real work. This guide uses Ubuntu’s packaged DokuWiki and Apache, then covers information architecture, backups and a routine suited to Australian schedules. Commands apply to Ubuntu releases using apt, with local network details called out where they affect the result.
Why a wiki suits a personal archive
DokuWiki turns individual notes into a browsable knowledge base. Namespaces act like folders, pages use readable text markup, and access-control lists can separate private drafts from shared material. Revision history lets you see when a decision changed, while search indexes titles and body text. Plugins can add tags, backlinks, task lists or a media library without changing the core format.
That durability matters for personal knowledge management. A publishing example is Abhay Chauhan’s site, where technical notes are presented as a coherent personal notebook. The same principle applies to a private wiki: show the context. A page headed ‘Router replacement’ should record the model, date, cable ports, firmware and reason for the decision, rather than leaving an unexplained fragment for future you.
Design for Australian English and local habits from the start. Use ‘organisation’, ‘licence’ as a noun and ‘practise’ as a verb; an arvo is an afternoon, while ‘have a go’ means trying an approach. Record time zones too: eastern states use AEST/AEDT, central Australia uses ACST/ACDT and Western Australia uses AWST. A timestamp with its zone prevents an ambiguous entry after daylight saving changes.
Preparing the Ubuntu host
Ubuntu Server is a compact base for a wiki serving a household or small team. Install a supported long-term-release version on a wired machine, give the server a fixed local address and reserve that address in the router. A laptop or Raspberry Pi is fine for a trial, but a small tower or mini PC with an SSD usually makes power recovery and maintenance easier.
Connect over SSH, refresh package metadata and install the web stack:
sudo apt update
sudo apt install dokuwiki apache2
sudo systemctl enable --now apache2
Ubuntu’s package keeps the application, configuration and user content in separate locations. Program files normally sit in /usr/share/dokuwiki, local settings in /etc/dokuwiki, and pages and attachments in /var/lib/dokuwiki/data. Plugins may have their own package directory. This layout means a replacement server can recover the knowledge base without copying every web-server file.
Create a normal administrator account and use SSH keys rather than accepting a password for remote access. A local DNS entry such as dokuwiki.home.arpa, backed by a router reservation, gives the machine a stable name without involving the public domain system. Keep console or recovery access available in case network changes leave the host unreachable.
Installing and securing the first release
The Ubuntu package normally exposes the wiki at /dokuwiki/ and may present its initial installer. Open http://localhost/dokuwiki/ on the host or use the reserved address from another computer. Follow the installer, create the administrator with a unique password, remove the generic welcome content and save a test page. Confirm that revisions appear before opening the site to other people.
Access control belongs in the initial setup. Rename any default account that could be guessed, disable public registration and assign permissions at namespace level. The web process needs read access to the program and configuration; the installation account should control changes to pages and attachments. Avoid chmod 777, which conceals incorrect ownership by granting everyone every permission.
Use HTTPS whenever traffic crosses the house or internet. NBN FTTP lines may receive a public address, while fixed-wireless and some 4G or 5G plans use carrier-grade NAT; household routers also block unsolicited connections by default. A WireGuard connection or a reverse proxy with a valid TLS certificate is safer than forwarding arbitrary ports. For local-only use, keep the service on the home network and require VPN access from elsewhere.
Plan for updates from the beginning. Enable Ubuntu’s unattended security upgrades, but review DokuWiki and plugin changes before an application upgrade because interface files, templates and stored markup can behave differently. A short maintenance window in a quiet period, with a known-good snapshot available, prevents a routine update from becoming an unplanned recovery job.
Building a structure that stays useful
Begin with a small set of namespaces: daily, projects, reference, media and admin. Add a new group only when pages have a shared purpose. Keep durable explanations separate from the day’s working notes, and use a wiki index page to explain what belongs in each area. This simple map prevents a personal wiki from becoming a searchable attic.
Templates reduce repetitive decisions. A meeting page can include date, attendees, decisions and actions; a recipe can include quantities, preparation time and dietary notes. Record the source of imported material and use tags sparingly, since a page title and namespace often provide enough structure. Stable filenames and descriptive attachment captions make old exports easier to search.
| Approach | Where content lives | Offline use | Sharing | Best fit |
|---|---|---|---|---|
| DokuWiki on Ubuntu | Readable page files and attachments on a server you control | Yes, through the server or a local copy | Browser or optional VPN | Long-lived, multi-device knowledge base |
| Plain Markdown folder | Individual text files in a synced folder | Excellent | File exchange or Git | Small, developer-centred archives |
| Cloud workspace | Proprietary database on a vendor account | Depends on the application | Strong sharing tools | Short-term collaboration and flexible layouts |
Images deserve the same care as text. Compress screenshots, remove private details and add useful alternative text before attaching them to a page. The archive’s GIMP review offers a period-specific look at a capable free graphics editor, although current releases use a different interface. Its practical value remains in showing how an open-source image tool can support a personal documentation workflow without a subscription.
Cost affects the choice in Australia. Many households already pay for cloud subscriptions, yet self-hosting can turn that recurring expense into modest hardware and electricity costs. A used mini PC bought through an Australian retailer or second-hand marketplace can run a small wiki for years. The labour is real, so people who need effortless team collaboration may still prefer a managed cloud workspace.
Backing up and restoring the archive
Protect the two things that cannot be recreated: page data and local configuration. The Ubuntu package makes a compact backup straightforward:
sudo tar -czf "$HOME/dokuwiki-data-$(date +%F).tar.gz" \
-C /var/lib/dokuwiki data
sudo tar -czf "$HOME/dokuwiki-config-$(date +%F).tar.gz" \
-C /etc dokuwiki
Move encrypted copies to an external drive or network-attached storage, and keep one off-site if the material matters. A second copy in another Australian city or region can protect against a local flood, fire or theft, but check the provider’s data-residency and access terms before placing personal notes in its cloud. Restrict shared folders with strong account credentials and multi-factor authentication where available.
Schedule backups daily and test a restore each quarter. A backup is useful only after someone verifies that the archive opens, pages render and attachments can be retrieved. Save the Ubuntu version, DokuWiki package version and plugin list alongside the files; recreating the exact environment on a new machine is then a documented process rather than a memory test.
Keep revisions for routine corrections, but use snapshots before bulk edits or plugin changes. The built-in history can recover one page; a filesystem snapshot can recover a whole namespace. Version history is not a substitute for backups, because deletion, corruption or a failed upgrade may affect many files at once.
Turning the setup into a weekly habit
Make capture easier than avoidance. Use the browser on a phone to add a note after a call, scan a warranty receipt into a dedicated inbox namespace, and file it during a short end-of-day routine. Tags can help with mobile items, but the destination namespace should be obvious. If capturing takes more than a minute, the workflow will be abandoned during a busy week in Sydney or on a regional trip.
Set aside a Friday arvo review, using the familiar Australian sense that a brief, no-worries check is enough rather than a large cleanup project. Clear the inbox namespace, finish or date unfinished tasks and add one sentence about why a decision was made. The aim is continuity: a modest ten-minute habit creates a much better archive than an occasional heroic weekend.
Keep the wiki broad enough to reflect your life, not just work. A page for a Blue Mountains walk, a garden calendar, a recipe or a software project can all use the same linking habits. Reusing templates and vocabulary lowers the effort of adding the next page. Search remains useful, but deliberate links answer questions that search alone cannot: what changed, why it changed and which related note should be read next.
Every few months, a light review keeps duplicate namespaces from accumulating and catches backups that have stopped running. Inactive projects can be archived while the core structure remains intact. The finished Ubuntu and DokuWiki installation is then less a software demonstration than a personal archive with dependable history, private access and a familiar structure that can travel with you.