How to Install Omeka Classic 2.4 CMS on Fedora 26 LAMP VPS

Prerequisites

Step 1: Add a Sudo User

Step 2: Update Fedora 26 System

Step 3: Install Apache Web Server

Step 4: Open Web Firewall Ports

Step 5: Disable SELinux

Step 6: Install PHP 7.1

Hapi 7: Instaloni serverin MariaDB (MySQL).

Hapi 8: Krijoni bazën e të dhënave për Omeka Classic CMS

Hapi 9: Instaloni skedarët Omeka Classic CMS

Hapi 10: Instaloni ImageMagick

Hapi 11: Plotësoni instalimin e Omeka Classic CMS

Omeka Classic 2.4 CMS is a free and open source digital publishing platform and Content Management System (CMS) for sharing digital collections and creating media-rich online exhibits. Omeka Classic 2.4 CMS enables scholars, librarians, archivists, museum professionals and cultural enthusiasts to create complex narratives and share rich collections and content at low cost without sacrificing design and technical quality. Omeka accepts and stores all types of files, including images, video, audio, multi-page documents, PDFs, Power Point presentations; and can handle large archives of metadata and files (with over 1 million items) with the only limitations being the power of your server.

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

Prerequisites

• Një shembull i pastër i serverit Vultr Fedora 26 me qasje SSH

Hapi 1: Shtoni një përdorues Sudo

Ne do të fillojmë duke shtuar një sudopërdorues të ri .

Së pari, hyni në serverin tuaj si root:

ssh root@YOUR_VULTR_IP_ADDRESS

Shto një përdorues të ri të quajtur user1(ose emrin e përdoruesit të preferuar):

useradd user1

Tjetra, vendosni fjalëkalimin për user1përdoruesin:

passwd user1

Kur të kërkohet, futni një fjalëkalim të sigurt dhe të paharrueshëm.

Tani kontrolloni /etc/sudoersskedarin për t'u siguruar që sudoersgrupi është i aktivizuar:

visudo

Kërkoni një seksion si ky:

%wheel        ALL=(ALL)       ALL

Sigurohuni që të jetë i pakomentuar. Kjo linjë na tregon se përdoruesit që janë anëtarë të wheelgrupit mund të përdorin sudokomandën për të fituar rootprivilegje.

Pasi të keni redaktuar skedarin, mund ta ruani dhe të dilni duke shtypur Escdhe më pas duke hyrë :wqpër të "shkruar" dhe "dalë" skedarin.

Më pas duhet të shtojmë user1në wheelgrup:

usermod -aG wheel user1

Ne mund të verifikojmë user1anëtarësimin në grup dhe të kontrollojmë nëse usermodkomanda ka funksionuar me groupskomandën:

groups user1

Tani përdorni sukomandën për të kaluar në user1llogarinë e re të përdoruesit sudo :

su - user1

Rreshti i komandës do të përditësohet për të treguar që tani jeni regjistruar në user1llogari. Ju mund ta verifikoni këtë me whoamikomandën:

whoami

Tani rinisni sshdshërbimin në mënyrë që të mund të identifikoheni sshme llogarinë e re të përdoruesit sudo jo-root që sapo keni krijuar:

sudo systemctl restart sshd

Dilni nga user1llogaria:

exit

Dilni nga rootllogaria (e cila do të shkëputë sshseancën tuaj ):

exit

Tani mund të sshhyni në shembullin e serverit nga hosti juaj lokal duke përdorur user1llogarinë e re të përdoruesit sudo jo-root :

ssh user1@YOUR_VULTR_IP_ADDRESS

Nëse dëshironi të ekzekutoni sudo pa pasur nevojë të shkruani një fjalëkalim çdo herë, atëherë hapni /etc/sudoersskedarin përsëri duke përdorur visudo:

sudo visudo

Redaktoni seksionin për wheelgrupin në mënyrë që të duket kështu:

%wheel        ALL=(ALL)       NOPASSWD: ALL

Ju lutemi vini re: Çaktivizimi i kërkesës së fjalëkalimit për përdoruesin sudo nuk është një praktikë e rekomanduar, por përfshihet këtu pasi mund ta bëjë konfigurimin e serverit shumë më të përshtatshëm dhe më pak zhgënjyes, veçanërisht gjatë seancave më të gjata të administrimit të sistemeve. Nëse jeni të shqetësuar për implikimet e sigurisë, gjithmonë mund ta ktheni ndryshimin e konfigurimit në origjinal pasi të keni përfunduar detyrat tuaja të administrimit.

Sa herë që dëshironi të hyni në rootllogarinë e përdoruesit nga brenda sudollogarisë së përdoruesit, mund të përdorni një nga komandat e mëposhtme:

sudo -i
sudo su -

Mund të dilni nga rootllogaria dhe të ktheheni në sudollogarinë tuaj të përdoruesit në çdo kohë duke shtypur thjesht sa vijon:

exit

Hapi 2: Përditësoni sistemin Fedora 26

Përpara se të instalojmë ndonjë paketë në shembullin e serverit Fedora, së pari do të përditësojmë sistemin.

Sigurohuni që jeni regjistruar në server duke përdorur një përdorues sudo jo-root dhe ekzekutoni komandën e mëposhtme:

sudo dnf -y update

Hapi 3: Instaloni Apache Web Server

Instaloni serverin në internet Apache:

sudo dnf -y install httpd

Pastaj përdorni systemctlkomandën për të nisur dhe aktivizuar Apache të ekzekutohet automatikisht në kohën e nisjes:

sudo systemctl enable httpd
sudo systemctl start httpd

Kontrolloni skedarin tuaj të konfigurimit të Apache për t'u siguruar që DocumentRootdirektiva tregon direktorinë e saktë:

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 Omeka Classic 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
</Directory>

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:

http://YOUR_VULTR_IP_ADDRESS/

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 Omeka Classic 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

Change SELINUX=enforcing to SELINUX=disabled and then save the file.

To apply the configuration change, SELinux requires a server reboot, so you can either restart the server using the Vultr control panel or you can simply use the shutdown command:

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 '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):

ssh user1@YOUR_VULTR_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 should 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 Omeka Classic 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 Omeka Classic 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 Omeka Classic CMS:

CREATE DATABASE omeka_db CHARACTER SET utf8 COLLATE utf8_general_ci;
CREATE USER 'omeka_user'@'localhost' IDENTIFIED BY 'UltraSecurePassword';
GRANT ALL PRIVILEGES ON omeka_db.* TO 'omeka_user'@'localhost';
FLUSH PRIVILEGES;
EXIT;

You can replace the database name omeka_db and username omeka_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 Omeka Classic 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:

pwd

Now use wget to download the Omeka Classic CMS installation package:

sudo wget https://github.com/omeka/Omeka/releases/download/v2.5.1/omeka-2.5.1.zip

Please note: You should definitely check for the most recent version by visiting the Omeka Classic 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 omeka-2.5.1.zip

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

sudo mv omeka-2.5.1/* /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

Now we're ready to move on to the final step.

Step 10: Install ImageMagick

Omeka Classic CMS requires ImageMagick to process images so let's make sure that it is installed:

sudo dnf -y install ImageMagick

Step 11: Complete Omeka Classic CMS Installation

1. To complete the Omeka Classic CMS installation, we first need to edit the Omeka Classic CMS database configuration file, so first make sure you are in the webroot and then open the db.ini file:

   sudo vi ./db.ini
   

   Replace the XXXXXXX values with your database configuration details, as follows:

   [database]
   host     = "localhost"
   username = "omeka_user"
   password = "UltraSecurePassword"
   dbname   = "omeka_db"
   prefix   = "omeka_"
   charset  = "utf8"
   ;port     = ""
   

   Once you have added the appropriate configuration values you can save and exit the configuration file.

2. Now visit the IP address of your server instance in your browser, or if you've already configured your Vultr DNS settings (and given it enough time to propagate) you can simply visit your domain instead.

   To access the Omeka Classic CMS installation page, enter your Vultr instance IP address into your browser address bar, followed by /install/:

       http://YOUR_VULTR_IP_ADDRESS/install/
   

3. On the Omeka Configure Your Site page, enter the following Default Superuser Account:

   Username:               <superuser username>
   Password:               <a secure password>
   Email:                  <superuser email address>
   

4. Next, enter the following Site Settings:

   Administrator Email:    <administrator email>
   Site Title:             <the title off the site>
   

   You can leave the rest of the Site Settings at their default values or you can edit them to suit your personal requirements.

5. When you are satisfied with the above site configuration details, click Install to finalize the installation.

You will be redirected to a Success page.

To access the admin section simply click on the Admin Dashboard button and enter your username and password. If you aren't redirected to the admin login page, you can enter the admin address manually:

http://YOUR_VULTR_IP_ADDRESS/admin/

You are now ready to start adding your content and configuring your materials and collections. Make sure you check out the excellent Omeka Classic CMS documentation for more information about how to build and configure your site.