Currently there are 17 entries in this BLOG.
Minor update to DokuWiki 2024-05-14 "Librarian" has been released (Changelog, Download). There are only some minor glitches so far.
And there are still some PHP 8.4 related problems in Plugins remaining as well.
Mostly trouble free update (Changelog, Download). There are only some minor glitches so far.
And there are some PHP 8.4 related problems in Plugins remaining as well.
Not surprising for those who follow the OpenBSD mailing lists, on 2025.04.28 OpenBSD 7.7 was released.
As usual the Upgrade instructions work fine and the first impression is good.
It is possible to use the deSEC IP Update API to update a wildcard subdomain.
This works basically the same as updating a normal subdomain. Just use * (asterisk) as the subdomain name in the hostname parameter, e.g.: *.example.com or *.sub.example.com. See Determine Hostname.
OpenBSD 7.6 has ports for Radicale 1.x and 2.x but none for the 3.x version.
After some of my own experiments and reading this thread on the misc@openbsd.org mailing list I have decided to publish the results on the GitHub Radicale wiki: Installing on OpenBSD.
Update: These instructions also work on OpenBSD 7.7.
Not surprising for those who follow the OpenBSD mailing lists, on 2024.10.08 OpenBSD 7.6 was released.
As usual the Upgrade instructions work fine and the first impression is good.
Not surprising for those who follow the OpenBSD mailing lists, on 2024.04.05 OpenBSD 7.5 was released.
As usual the Upgrade instructions work fine and the first impression is good.
It is interesting to note that the first patch was available before the release, even though its date is noted as April 8, 2024. So for once running syspatch(8) immediately after upgrading or installing OpenBSD will actually apply a patch.
Many operating systems (OSes) have package managers that offer a DokuWiki package.
The advantages of using such a package are:
But there are disadvantages as well:
So an admin needs to decide whether to use an OS package or a manual method for installing DokuWiki.
Using the package is generally easier and gets your DokuWiki up and running faster. But for best results it may be better to install DokuWiki manually.
Tip: Install DokuWiki using a package and note the OS-specific things this package does. Then apply that to your manual install. This wastes a bit of disk space by having an unused version of DokuWiki and potentially some unused dependencies installed. But in most cases that is negligible.
Note 1: The following may partially apply to other UN*X operating systems as well with minor adaptations.
Note 2: As a general rule, before making significant changes to your wiki, make sure you have a good backup. A simple copy (including file system permissions) of your DokuWiki root directory will suffice.
DokuWiki is available as a port on OpenBSD. So the seemingly easiest way to update is to execute:
$ doas pkg_add -u.
There are two drawbacks though:
dokuwiki-2023.04.04p0 ("Jack Jackrum") while the latest offcial release is DokuWiki 2024-02-06a "Kaos"./var/www/dokuwiki/ you are out of luck.
You could use the upgrade Plugin. However that requires the whole DokuWiki directory tree to be writable by the web server. Personally I feel that this is a potential security issue. though not exploitable on its own.
So IMHO it makes sense to decouple the OpenBSD port from the running instance(s) of DokuWiki. You could let your DokuWiki live in e.g. /var/www/mywiki/ or, if you use a web server other than the chroot(2)ed httpd(8), /home/my-web-user/mywiki/.
You could still install the OpenBSD port just to get all of the minimum dependencies taken care of. But you might just as well install the dependencies manually. (This would also allow you to set up a more modern version of PHP for DokuWiki instead of the default version corresponding with the particular OpenBSD release.)
So I have come up with a script to handle the updates. This script downloads the latest stable release of DokuWiki, sets the permissions (minimal required for correct operation of the wiki), updates a working DokuWiki instance and does cleanup such as deleting files that are no longer needed.
See GitHub for the actual script.
It may be a good idea to invalidate the DokuWiki caches after the upgrade. This can be accomplished simply by saving the DokuWiki configuration.