Learn How To Install ProcessWire CMS 3.0 on a Fedora 26 LAMP VPS

July 30, 2019

Table of Contents

If you are using a different system, please check our other tutorials.

ProcessWire CMS 3.0 is a simple, flexible and powerful, free and open source Content Management System (CMS). ProcessWire CMS 3.0 features an easy-to-use jQuery-style API, fully modular plugin architecture, and a flexible and powerful templating system that delivers an equally satisfying user experience for designers, developers, and end-users.

In this tutorial we are going to install ProcessWire CMS 3.0 on a Fedora 26 LAMP VPS using Apache web server, PHP 7.1, and a MariaDB database.


  • A clean IT Web Services Fedora 26 server instance with SSH access

Step 1: Add a Sudo User

We will start by adding a new sudo user.

First, log into your server as root:


Add a new user called user1 (or your preferred username):

useradd user1

Next, set the password for the user1 user:

passwd user1

When prompted, enter a secure and memorable password.

Now check the /etc/sudoers file to make sure that the sudoers group is enabled:


Look for a section like this:

%wheel        ALL=(ALL)       ALL

And make sure it is uncommented. This line tells us that users who are members of the wheel group can use the sudo command to gain root privileges.

Once you have edited the file, you can save and exit by pressing Esc and then entering :wq to “write” and “quit” the file.

Next we need to add user1 to the wheel group:

usermod -aG wheel user1

We can verify the user1 group membership and check that the usermod command worked with the groups command:

groups user1

Now use the su command to switch to the new sudo user user1 account:

su - user1

The command prompt will update to indicate that you are now logged into the user1 account. You can verify this with the whoami command:


Now restart the sshd service so that you can login via ssh with the new non-root sudo user account you have just created:

sudo systemctl restart sshd

Exit the user1 account:


Exit the root account (which will disconnect your ssh session)


You can now ssh into the server instance from your local host using the new non-root sudo user user1 account:


If you want to execute sudo without having to type a password every time, then open the /etc/sudoers file again, using visudo:

sudo visudo

Edit the section for the wheel group so that it looks like this:

%wheel        ALL=(ALL)       NOPASSWD: ALL

Please note: Disabling the password requirement for the sudo user is not a recommended practice, but it is included here as it can make server configuration much more convenient and less frustrating, especially during longer systems administration sessions. If you are concerned about the security implications, you can always revert the configuration change to the original after you finish your administration tasks.

Whenever you want to log into the root user account from within the sudo user account, you can use one of the following commands:

sudo -i
sudo su -

You can exit the root account and return back to your sudo user account any time by simply typing exit.

Step 2: Update Fedora 26 System

Before installing any packages on the Fedora server instance, we will first update the system.

Make sure you are logged in to the server using a non-root sudo user and run the following command:

sudo dnf -y update

Step 3: Install Apache Web Server

Install the Apache web server:

sudo dnf -y install httpd

Use the systemctl command to start and enable Apache to execute automatically at boot time:

sudo systemctl enable httpd
sudo systemctl start httpd

Check your Apache configuration file to ensure that the DocumentRoot directive points to the correct directory:

sudo vi /etc/httpd/conf/httpd.conf

The DocumentRoot configuration option will look like this:

DocumentRoot "/var/www/html"

Now, let’s make sure that the mod_rewrite Apache module is loaded. We can do this by searching the Apache base modules configuration file for the term “mod_rewrite“.

Open the file:

sudo vi /etc/httpd/conf.modules.d/00-base.conf

Search for the term mod_rewrite.

If the mod_rewrite Apache module is loaded, you will find a configuration line looking like this:

LoadModule rewrite_module modules/mod_rewrite.so

If the above line starts with a semi-colon, you will need to remove the semi-colon to uncomment the line and load the module. This, of course, applies to any other required Apache modules too.

We now need to edit Apache’s default configuration file so that mod_rewrite will work correctly with ProcessWire CMS.

Open the file:

sudo vi /etc/httpd/conf/httpd.conf

Then find the section that starts with <Directory "/var/www/html"> and change AllowOverride none to AllowOverride All. The end result (with all comments removed) will look something like this:

<Directory "/var/www/html">
    Options Indexes FollowSymLinks
    AllowOverride All
    Require all granted

Now save and close the Apache configuration file.

We will restart Apache at the end of this tutorial, but restarting Apache regularly during installation and configuration is certainly a good habit, so let’s do it now:

sudo systemctl restart httpd

Step 4: Open Web Firewall Ports

We now need to open the default HTTP and HTTPS ports as they will be blocked by firewalld by default.

Open the firewall ports:

sudo firewall-cmd --permanent --add-port=80/tcp
sudo firewall-cmd --permanent --add-port=443/tcp

Reload the firewall to apply the changes:

sudo firewall-cmd --reload

You will see the word success displayed in your terminal after each successful firewall configuration command.

We can quickly verify that the Apache HTTP port is open by visiting the IP address or domain of the server instance in a browser:


You will see the default Apache web page in your browser.

Step 5: Disable SELinux

SELinux stands for “Security Enhanced Linux”. It is a security enhancement to Linux which allows users and administrators more control over access control. It is enabled by default in Fedora 26, but it is definitely not essential for server security as many Linux server distributions do not ship with it installed or enabled by default.

To avoid file permission problems with ProcessWire CMS later down the line, we are going to disable SELinux, for now. So open the SELinux configuration file with your favourite terminal editor:

sudo vi /etc/selinux/config

And change SELINUX=enforcing to SELINUX=disabled, then save the file.

To apply the configuration change, SELinux requires a server reboot, so you can either restart the server using the IT Web Services control panel or you can simply use the shutdown command to cleanly shutdown and restart the server:

sudo shutdown -r now

When the server reboots, your SSH session will get disconnected and you may see a message informing you about a 'broken pipe' or informing you 'Connection closed by remote host'. This is nothing to worry about, simply wait for 20 seconds or so and then SSH back in again (with your own username and domain):

ssh user1@YOUR_DOMAIN

Or (with your own username and IP address):


Once you have logged back in, you should check the status of SELinux with the sestatus command to make sure it is properly disabled:

sudo sestatus

You will see a message saying SELinux status: disabled. If you see a message saying SELinux status: enabled (or something similar) you will need to repeat the above steps and ensure that you properly restart your server.

Step 6: Install PHP 7.1

We can now install PHP 7.1 along with all of the necessary PHP modules required by ProcessWire CMS.

sudo dnf -y install php php-mysqlnd php-mbstring php-gd php-common php-pdo php-pecl-imagick php-xml php-zip

Step 7: Install MariaDB (MySQL) Server

Fedora 26 defaults to using MariaDB database server, which is an enhanced, fully open source, community developed, drop-in replacement for MySQL server.

Install MariaDB database server:

sudo dnf -y install mariadb-server

Start and enable MariaDB server to execute automatically at boot time:

sudo systemctl enable mariadb
sudo systemctl start mariadb    

Secure your MariaDB server installation:

sudo mysql_secure_installation

The root password will be blank, so simply hit enter when prompted for the root password.

When prompted to create a MariaDB/MySQL root user, select “Y” (for yes) and then enter a secure root password. Simply answer “Y” to all of the other yes/no questions as the default suggestions are the most secure options.

Step 8: Create Database for ProcessWire CMS

Log into the MariaDB shell as the MariaDB root user by running the following command:

sudo mysql -u root -p

To access the MariaDB command prompt, simply enter the MariaDB root password when prompted.

Run the following queries to create a MariaDB database and database user for ProcessWire CMS:

CREATE USER 'pw_user'@'localhost' IDENTIFIED BY 'UltraSecurePassword';
GRANT ALL PRIVILEGES ON pw_db.* TO 'pw_user'@'localhost';

You can replace the database name pw_db and username pw_user with something more to your liking, if you prefer. Also, make sure that you replace “UltraSecurePassword” with an actually secure password.

Step 9: Install ProcessWire CMS Files

Change your current working directory to the default web directory:

cd /var/www/html/

If you get an error message saying something like 'No such file or directory' then try the following command:

cd /var/www/ ; sudo mkdir html ; cd html

Your current working directory will now be: /var/www/html/. You can check this with the pwd (print working directory) command:


Now use wget to download the ProcessWire CMS installation package:

sudo wget https://github.com/processwire/processwire/archive/master.zip

Please note: You should definitely check for the most recent version by visiting the ProcessWire CMS download page.

List the current directory to check that you have successfully downloaded the file:

ls -la

Let’s quickly install unzip so we can unzip the file:

sudo dnf -y install unzip

Now uncompress the zip archive:

sudo unzip master.zip

Move all of the installation files to the web root directory:

sudo mv processwire-master/* /var/www/html

Change ownership of the web files to avoid any permissions problems:

sudo chown -R apache:apache * ./

Restart Apache again:

sudo systemctl restart httpd

Step 10: Complete ProcessWire CMS Installation

It’s now time to visit the IP address of your server instance in your browser, or if you’ve already configured your IT Web Services DNS settings (and given it enough time to propagate) you can simply visit your domain instead.

To access the ProcessWire CMS installation page, enter your IT Web Services instance IP address into your browser address bar, followed by index.php:


The ProcessWire CMS installer contains a lot of options, so here are a few pointers to help you along:

  1. On the ProcessWire CMS installation welcome page, click the Get Started button to start the installation process.

  2. Now select your preferred installation profile (or demo site) and click Continue.

  3. You will see a Compatibility Check page. If you see any errors, it probably means you are missing some PHP modules or have a permissions problem, otherwise you can simply click Continue.

  4. Enter the following values into the MySQL Database Settings page:

    DB Name:            pw_db
    DB User:            pw_user
    DB Pass:            UltraSecurePassword
    DB Host:            localhost
    DB Port:            3306
  5. You can leave the File Permission settings at their default values, or you can adjust them if you understand the implications.

  6. You can enter the future hostnames of your site in the appropriate section, or you can edit the site/config.php file later if you prefer.

  7. Click on Continue to configure the database and install the ProcessWire CMS files.

  8. Next, select your preferred Admin Theme.

  9. You can change the Admin URL if you prefer, or you can simply leave it at the default value.

  10. Enter your Admin Login Details as shown below:

    User (a-z 0-9):     <admin username>
    Password:           <admin password>
    Password (again):   <same admin password>
    Email Address:      <admin email address>
  11. Once all of the appropriate details have been entered, you can click Continue to finalize the ProcessWire installation.

  12. Once the installation is complete, simply click on the Login to Admin button to log in the the Admin section.

You may see a warning saying something like:

Warning: your server locale is undefined and may cause issues. Please add this to /site/config.php file (adjust en_US.UTF-8†as needed): setlocale(LC_ALL,'en_US.UTF-8');

You can fix this error by editing the site/config.php file:

sudo vi site/config.php

Append the appropriate value to the end of the file:


If you can’t figure out what value to use, you can find a list of appropriate values for your particular server instance by running the locale command:

locale -a

Don’t forget to save and exit the site/config.php file when you are finished editing.

For security purposes, make sure you change the permissions on the site/config.php file:

sudo chmod 400 site/config.php

Restart Apache.

sudo systemctl restart httpd

You are ready to start adding your content and configuring the look and feel of your site. Make sure you check out the excellent ProcessWire CMS documentation for more information about how to build and configure your site.

Need help?

Do you need help setting up this on your own service?
Please contact us and we’ll provide you the best possible quote!