How to Install Tiki Wiki CMS Groupware 30 LTS on AlmaLinux 9 or Rocky Linux 9
Install Tiki Wiki CMS Groupware 30 LTS on AlmaLinux 9 or Rocky Linux 9 with Apache, MariaDB and PHP 8.3, setup.sh permissions, SELinux labels and the web installer.
This guide installs Tiki Wiki CMS Groupware 30 LTS on AlmaLinux 9, Rocky Linux 9 or CentOS Stream 9 with Apache, MariaDB and PHP 8.3. At the end you will have Tiki running under its own virtual host with correct file permissions, SELinux still enforcing, and the web installer locked. CentOS 7 reached end of life in June 2024, and its PHP and MariaDB versions are far too old for any supported Tiki release, so a RHEL 9 compatible system replaces it here.
Which Tiki version to install
Tiki publishes a new major version roughly twice a year and designates some of them as long-term support (LTS) releases. At the time of writing:
| Version | Type | PHP | Database |
|---|---|---|---|
| Tiki 30 | LTS, current (30.2) | 8.1 to 8.4 | MariaDB 10.5+ or MySQL 8.0+ |
| Tiki 27 | LTS (27.9), security fixes until 2029 | 8.1 to 8.4 | MariaDB 10.5+ or MySQL 8.0+ |
| Tiki 24 | LTS, security fixes until 2027 | 7.4 only | MariaDB 5.5+ or MySQL 5.7+ |
This guide installs Tiki 30, the newest LTS with the longest remaining support (until 2031). The project's download page still labels the older 27.x LTS as its recommended version; if you want the most conservative choice, the steps below work unchanged for Tiki 27 because its requirements are the same, and only the download folder (Tiki_27.x_Miaplacidus) and version number differ. AlmaLinux 9 and Rocky Linux 9 provide PHP 8.3 as an AppStream module stream and MariaDB 10.5 as the default database server, which both fall inside the supported range.
Requirements
- A server running AlmaLinux 9, Rocky Linux 9 or CentOS Stream 9. Plan for at least 2 GB of RAM; Tiki is a large application.
- A user with
sudorights (the examples usedeploy). - A host name such as
wiki.example.compointing to the server.
sudo dnf -y updateInstall Apache, MariaDB and PHP 8.3
The default PHP on these systems is 8.0, which Tiki 30 does not support. Enable the 8.3 module stream first:
sudo dnf -y module reset php
sudo dnf -y module enable php:8.3
sudo dnf -y install httpd mariadb-server policycoreutils-python-utils tar \
php php-mysqlnd php-gd php-intl php-mbstring php-xml php-pecl-zip \
php-curl php-opcache php-bcmathTiki's dependency list requires the calendar, curl, dom, fileinfo, gd, iconv, intl, json, libxml, openssl and zip extensions. The packages above cover all of them; several are part of php-common. On RHEL 9 compatible systems Apache runs PHP through PHP-FPM, which is pulled in by the php package.
Start the services and open the firewall:
sudo systemctl enable --now mariadb php-fpm httpd
sudo firewall-cmd --permanent --add-service=http --add-service=https
sudo firewall-cmd --reloadCreate the database
sudo mariadb-secure-installation
sudo mariadbCREATE DATABASE tiki CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'tiki'@'localhost' IDENTIFIED BY 'change-this-password';
GRANT ALL PRIVILEGES ON tiki.* TO 'tiki'@'localhost';
EXIT;Download Tiki and set permissions
Release archives are hosted on the project's SourceForge page. The packaged archives already contain all third-party libraries, so Composer is not needed (it is only required for Git checkouts). Check tiki.org/Download for the newest 30.x release and adjust the version number:
cd /tmp
curl -L -o tiki-30.2.tar.gz \
https://downloads.sourceforge.net/project/tikiwiki/Tiki_30.x_Alpheratz/30.2/tiki-30.2.tar.gz
sudo mkdir -p /var/www/tiki
sudo tar -xzf tiki-30.2.tar.gz -C /var/www/tiki --strip-components 1Tiki ships a script, setup.sh, that sets ownership and permissions for the whole tree. Run it from the Tiki directory and tell it that the web server user and group are apache; the fix command applies the standard permission model:
cd /var/www/tiki
sudo sh setup.sh -u apache -g apache fixRun sh setup.sh -h to see the other switches. The same command repairs permissions later, for example after an upgrade.
SELinux is enforcing by default and only lets the web server write to files labelled for it. Tiki writes to many places inside its tree (configuration in db, caches in temp, uploads in storage and others, themes and templates), so the simplest reliable approach is to label the application directory as writable web content, and to allow outgoing connections and mail, which Tiki uses for profiles, feeds and notifications:
sudo semanage fcontext -a -t httpd_sys_rw_content_t "/var/www/tiki(/.*)?"
sudo restorecon -R /var/www/tiki
sudo setsebool -P httpd_can_network_connect 1
sudo setsebool -P httpd_can_sendmail 1Configure Apache
Create /etc/httpd/conf.d/tiki.conf. AllowOverride All lets Tiki's .htaccess file (clean URLs and access restrictions for internal files) take effect:
<VirtualHost *:80>
ServerName wiki.example.com
DocumentRoot /var/www/tiki
<Directory /var/www/tiki>
Options -Indexes +FollowSymLinks
AllowOverride All
Require all granted
</Directory>
</VirtualHost>Tiki keeps its reference rules in a file named _htaccess and expects .htaccess to be a link or copy of it. The installer offers to set this up; if you prefer to do it by hand, the method Tiki recommends is a symbolic link, so the rules stay current after upgrades:
cd /var/www/tiki
sudo ln -s _htaccess .htaccesssudo apachectl configtest
sudo systemctl restart php-fpm httpdRun the web installer
Open http://wiki.example.com/tiki-install.php and follow the steps:
- Select the language and accept the licence (LGPL).
- Review the requirements page. It reports missing PHP extensions and settings worth raising, such as
memory_limitand upload sizes. To change them, add a file such as/etc/php.d/99-tiki.iniand restartphp-fpm. - Enter the database connection: host
localhost, databasetiki, usertikiand its password. - Install the database and choose the default profile unless you know you need another.
- Fill in the general settings (site title, sender email, HTTPS preference).
- Finish and enter Tiki. The installer locks itself at this point so that it cannot be run again by a visitor.
The initial account is admin with the password admin. Tiki forces you to choose a new password at the first login; do it straight away, because the site is reachable from the internet at this point.
After installation
- Add a TLS certificate (for example from Let's Encrypt with Certbot) and then require HTTPS for logins in the Tiki security settings.
- Enable only the features you need under Control Panels. Tiki has several hundred optional features and each one adds attack surface.
- Open Control Panels > Security and the server check page (
tiki-check.php) and work through the warnings. - Back up the database and the Tiki directory regularly:
sudo mariadb-dump tiki | gzip > ~/tiki-$(date +%F).sql.gzand an archive of/var/www/tiki, which containsdb/local.phpand uploaded files.
Upgrading within Tiki 30
Minor releases (30.2 to 30.3 and so on) are installed by unpacking the new archive over the existing directory after a backup, re-running setup.sh, and updating the database schema from the command line:
cd /var/www/tiki
sudo sh setup.sh -u apache -g apache fix
sudo -u apache php console.php database:update
sudo restorecon -R /var/www/tikiMajor upgrades, for example from one LTS to the next, follow the same pattern but deserve a test run on a copy of the site first. Read the upgrade notes for the target version in the Tiki upgrade documentation.
Frequently asked questions
Should I pick the LTS or the newest release?
Tiki's own advice is to use an LTS version if you want the fewest changes and to move to the next LTS shortly before the old one reaches end of life. Tiki 30 is the newest LTS; Tiki 27 is the previous one and has had more time to mature. Non-LTS versions such as the upcoming Tiki 31 are only supported until shortly after the next version appears, so avoid them unless you intend to upgrade every few months.
Can I use Nginx instead of Apache?
Tiki runs behind Nginx with PHP-FPM, but Nginx does not read .htaccess. You have to translate the rewrite and deny rules from _htaccess into the server block yourself and keep them in sync after upgrades. Apache is the path with the least manual work.
Is labelling the whole Tiki directory writable for SELinux safe?
It is less strict than labelling individual directories, but far better than disabling SELinux. Ordinary file permissions set by setup.sh still apply. If you want a tighter policy, label only the directories that setup.sh makes writable and test every feature you use, since uploads, caching, themes and package installation each write to different paths.
The installer page is blank or shows a 500 error. Where do I look?
Check /var/log/httpd/error_log and /var/log/php-fpm/www-error.log for the PHP error, and /var/log/audit/audit.log for SELinux denials. A missing extension or a PHP version outside 8.1 to 8.4 are the usual causes.