Set up a personal wiki with Wiki.js on Ubuntu
A personal wiki gives you one searchable, self-hosted home for project notes, reading lists, meeting records, recipes and the small pieces of knowledge you never want to lose. Unlike a folder of documents, it links ideas together, supports tags and templates, and remains available through a browser on the computers and phones you already use.
This guide shows how to set up a personal wiki with Wiki.js on Ubuntu, using Docker Compose so installation, storage and upgrades stay predictable. You will end with a private, browser-based workspace that keeps its database and files on your own hardware, works well for one household, and can be reached from a laptop in Brisbane or a phone on an Australian train without handing control to a hosted note service.
Prepare Ubuntu and plan the installation
Ubuntu 24.04 LTS is a practical base for this project. Update the machine, install the packages that manage containers, and make sure the system has a stable address or name on your home network. Wired Ethernet is preferable for an always-on server, although Wi-Fi is fine for testing.
sudo apt update
sudo apt install -y docker.io docker-compose-v2
sudo systemctl enable --now docker
sudo usermod -aG docker "$USER"
After changing group membership, sign out and back in so it takes effect. You can also run newgrp docker in the current terminal.
Choose where the wiki will live. A spare laptop or low-power mini PC sold by Australian retailers such as JB Hi-Fi, Umart or Amazon Australia can run it quietly in a cupboard, while a desktop gives you more storage headroom. Keep the server near your router, use a UPS if outages are common, and reserve several gigabytes for the database, uploaded images and backups. SQLite suits a personal or small-family wiki; a larger team should consider PostgreSQL.
Treat the wiki as a records system if other people will use it. The federal Privacy Act 1988 and Australian Privacy Principles regulate many organisations that handle personal information, while an individual’s purely personal notes generally fall outside that regime. A business, health service, club or community project may also fall under state and territory privacy laws, such as the Privacy and Personal Information Protection Act 1998 in NSW or the Information Privacy Act 2009 in Queensland. Restrict sensitive pages, set a deletion policy and check retention duties if a public office or regulated organisation uses the wiki.
Launch Wiki.js with Docker Compose
Create a working directory and open a text editor. Save the following configuration as compose.yaml inside that directory. The volume maps a folder in your home directory to the wiki’s data directory, while the port is initially limited to the Ubuntu machine itself.
mkdir -p ~/wiki/data
cd ~/wiki
nano compose.yaml
services:
wiki:
image: ghcr.io/requarks/wiki:2
container_name: personal-wiki
restart: unless-stopped
ports:
- "127.0.0.1:3000:3000"
environment:
- DB_TYPE=sqlite
- DB_FILE=/wiki/data/wiki.db
volumes:
- ./data:/wiki/data
Start the service and inspect its status. The first launch can take a minute while Docker downloads the image and initialises the database.
docker compose up -d
docker compose ps
If Compose reports that the docker command is not allowed, confirm that your group membership is active. A permission error on data usually means the container cannot write there, so check ownership rather than giving the container unnecessary privileges. Use docker compose logs --tail=100 wiki to read startup messages and confirm that the SQLite database was created.
Configure the site for private use
Open http://localhost:3000 on the Ubuntu machine and complete the first-run wizard. On a headless server, you can instead create an SSH tunnel with ssh -L 3000:localhost:3000 ubuntu@server-ip and open the same address in your browser. Create the administrator account with a unique password stored in a password manager, choose a descriptive site title and select English, or English (Australia) if available.
For a private family wiki, set page security to private or restricted, disable open account registration and retain the built-in local authentication method. If you later connect Google, Microsoft or another identity provider, check that its account and group rules match the access you intend. Local authentication is straightforward, but a second administrator for the household can prevent lockouts when one person replaces a shared credential.
In the storage panel, keep the bundled local-filesystem option and ensure its path points inside the container’s /wiki/data location. Do not change the database backend during normal operation because the Compose file is configured for SQLite. Disable analytics if you prefer not to send usage data, and set the correct site URL before enabling remote access. This prevents Wiki.js from generating links that point back to localhost on another device.
Create pages that stay easy to find
The editor supports Markdown, so a page can begin with # Project notes and use ordinary headings, lists, links, tables, code blocks and images. A useful first structure is a Home page linking to Projects, Reference, Journal and People. Create a template for recurring notes, such as a meeting record with fields for date, attendees, decisions and actions, rather than rebuilding the same headings each time.
Paths and tags answer different questions. A path such as /projects/garden-shed shows where a page belongs; tags such as hardware, family or to-read let one page appear in several filtered views. Keep names short, avoid duplicating nearly identical pages and use redirects when information moves. Full-text search indexes page content, while the dashboard and recent-changes views make it easy to return to material edited on another device.
Capture details in a form that will still make sense later. Under the day-first convention used across Australia, 04/03/2026 means 4 March, or you can spell out the month. Record times with AEST or AEDT where daylight saving matters and label amounts with A$. Tags for NSW, VIC, QLD and SA can help organise travel information or household projects. A consistent title, location and amount of context matter more than a complicated hierarchy.
Reach the wiki from your devices
For access around the house, find the Ubuntu host’s address with hostname -I, then use http://that-address:3000 from another device. Change the Compose port mapping from 127.0.0.1:3000:3000 to 0.0.0.0:3000:3000, restart the service and, if Ubuntu Firewall is enabled, permit port 3000 only from your trusted home network. Many Australian NBN plans use a router supplied by Telstra, Optus or another provider; its DHCP reservation screen can keep the Ubuntu machine on the same local address.
Do not assume that a home internet plan provides an inbound route to your server. Some NBN technologies, especially FTTN, FTTC and fixed wireless, place the connection behind carrier-grade NAT, while other services provide a dynamic public address. A port-forwarding rule on the router will not work under CGNAT. For reliable access away from home, a private mesh network such as Tailscale or WireGuard is safer than exposing Wiki.js directly to the internet.
A secure mesh connection also suits everyday Australian movement: check the wiki from a phone tethering through a hotspot on the train or read notes while waiting for a flat white in a Melbourne or Sydney café. Keep the phone screen private, use a strong hotspot password and avoid entering the administrator password on a shared device. Save the site as a browser bookmark or install it as a Progressive Web App where supported. You gain the same searchable material without maintaining a separate mobile wiki.
Protect, maintain and remember the system
Back up the entire data directory, not just exported pages. It contains the SQLite database, configuration and uploaded assets. A short downtime gives you a consistent archive on a single-user system, and an encrypted copy on an external drive or cloud-storage folder reduces the risk from one failed disk.
cd ~/wiki
docker compose stop
tar -czf "wiki-backup-$(date +%F).tgz" data
docker compose start
Keep several dated backups and check that the important files can be opened. To restore, stop the container, preserve the current directory under a different name, extract the archive over data and start the service again. This restores the database and media as a matched set. Wiki.js page exports are useful for moving selected content elsewhere, but they do not replace a full backup of accounts, settings and attachments.
Check the container logs and free disk space periodically. Before an upgrade, make a fresh backup and read the release notes, then pull the current image and recreate the service.
docker compose pull
docker compose up -d
docker compose ps
Use a current Ubuntu LTS release, update Docker and the host regularly, and remove old backup archives once newer copies have been verified. Remember the core principle: keep access private, pages organised and backups verified, so the information remains available and trustworthy long after the installation day.