How to install Omeka CMS on Ubuntu 21.04
- 00:41 lsb_release -a
- 00:54 mysql -u root -p
- 01:10 create database omeka;
- 01:21 use omeka;
- 01:31 create user ouser@localhost identified by 'linuxc';
- 01:56 grant all on omeka.* to ouser@localhost;
- 02:10 flush privileges;
- 02:18 exit
- 02:28 wget https://github.com/omeka/omeka-s/releases/download/v1.4.0/omeka-s-1.4.0.zip
- 02:42 unzip omeka-s-1.4.0.zip
- 02:59 mv omeka-s /var/www/omeka
- 03:07 chown -R www-data. /var/www/omeka
- 03:23 chmod -R 775 /var/www/omeka
- 03:40 vi /etc/apache2/sites-available/omeka.conf
- 04:13 a2dissite 000-default.conf
- 04:28 a2ensite omeka.conf
- 04:42 a2enmod rewrite
- 04:58 vi /var/www/omeka/config/database.ini
- 05:27 systemctl restart apache2
- 05:35 vi /etc/hosts
To Install Omeka CMS on Ubuntu 21.04
Introduction
The content management system is software used to manage digital content. It is an open-source content management system and web publishing platform that allows the display of library, museum, scholarly, and archival collections.
Prerequisites:
• Apache Web server
• Maria DB
• PHP and its Modules
Installation Procedure:
Step 1: Check the OS version by using the following command
root@linuxhelp:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 21.04
Release: 21.04
Codename: hirsute
Step 2: Log in to the Maria DB
root@linuxhelp:~# mysql -u root -p
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 30
Server version: 10.5.12-MariaDB-0ubuntu0.21.04.1 Ubuntu 21.04
Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
Step 3: Create database for omeka CMS
MariaDB [(none)]> create database omeka;
Query OK, 1 row affected (0.011 sec)
Step 4: Select the omeka database
MariaDB [(none)]> use omeka;
Database changed
Step 5: Create a user named “ouser”
MariaDB [omeka]> create user ouser@localhost identified by 'linuxc';
Query OK, 0 rows affected (0.024 sec)
Step 6: Grant all privileges on omeka database for the user “ouser”
MariaDB [omeka]> grant all on omeka.* to ouser@localhost;
Query OK, 0 rows affected (0.004 sec)
Step 7: Flush privileges to make changes effect
MariaDB [omeka]> flush privileges;
Query OK, 0 rows affected (0.004 sec)
Step 8: Exit from the Maria DB
MariaDB [omeka]> exit
Bye
Step 9: Download omeka CMS by using the following command
root@linuxhelp:~# wget https://github.com/omeka/omeka-s/releases/download/v1.4.0/omeka-s-1.4.0.zip
--2021-11-26 02:33:59-- https://github.com/omeka/omeka-s/releases/download/v1.4.0/omeka-s-1.4.0.zip
Resolving github.com (github.com)... 13.234.210.38
Connecting to github.com (github.com)|13.234.210.38|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://objects.githubusercontent.com/github-production-release-asset-2e65be/12057192/15fe4f80-5ad6-11e9-8bc2-a6804b988866?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211125%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211125T210359Z&X-Amz-Expires=300&X-Amz-Signature=486aa3498f50d4a79bd50343a0d9d3a7d35d9f492ac2ca0793932244a875a0f0&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=12057192&response-content-disposition=attachment%3B%20filename%3Domeka-s-1.4.0.zip&response-content-type=application%2Foctet-stream [following]
--2021-11-26 02:33:59-- https://objects.githubusercontent.com/github-production-release-asset-2e65be/12057192/15fe4f80-5ad6-11e9-8bc2-a6804b988866?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211125%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211125T210359Z&X-Amz-Expires=300&X-Amz-Signature=486aa3498f50d4a79bd50343a0d9d3a7d35d9f492ac2ca0793932244a875a0f0&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=12057192&response-content-disposition=attachment%3B%20filename%3Domeka-s-1.4.0.zip&response-content-type=application%2Foctet-stream
Resolving objects.githubusercontent.com (objects.githubusercontent.com)... 185.199.110.133, 185.199.111.133, 185.199.109.133, ...
Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|185.199.110.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14052203 (13M) [application/octet-stream]
Saving to: ‘omeka-s-1.4.0.zip’
omeka-s-1.4.0.zip 100%[===================================================>] 13.40M 10.5MB/s in 1.3s
2021-11-26 02:34:02 (10.5 MB/s) - ‘omeka-s-1.4.0.zip’ saved [14052203/14052203]
Step 10: Extract the downloaded file in omeka directory
root@linuxhelp:~# unzip omeka-s-1.4.0.zip
Archive: omeka-s-1.4.0.zip
inflating: omeka-s/.htaccess
inflating: omeka-s/LICENSE
inflating: omeka-s/README.md
inflating: omeka-s/bootstrap.php
inflating: omeka-s/cli-config.php
inflating: omeka-s/composer.json
inflating: omeka-s/composer.lock
inflating: omeka-s/index.php
inflating: omeka-s/application/Module.php
inflating: omeka-s/config/database.ini
inflating: omeka-s/config/local.config.php
inflating: omeka-s/files/index.html
inflating: omeka-s/logs/application.log
inflating: omeka-s/logs/sql.log
Step 11: Move the Extracted files to the Apache home directory
root@linuxhelp:~# mv omeka-s /var/www/omeka
Step 12: Change Ownership to the omeka directory
root@linuxhelp:~# chown -R www-data. /var/www/omeka
Step 13: Change Permissions to the omeka directory
root@linuxhelp:~# chmod -R 775 /var/www/omeka
Step 14: Create Virtual Host for the omeka CMS
root@linuxhelp:~# vi /etc/apache2/sites-available/omeka.conf
<virtualhost *:80>
servername www.linuxhelp1.com
documentroot /var/www/omeka
<Directory /var/www/omeka>
AllowOverride All
allow from all
</Directory>
</virtualhost>
Step 15: Disable the default Virtual Host file of apache
root@linuxhelp:~# a2dissite 000-default.conf
Site 000-default disabled.
To activate the new configuration, you need to run:
systemctl reload apache2
Step 16: Enable the Virtual Host
root@linuxhelp:~# a2ensite omeka.conf
Enabling site omeka.
To activate the new configuration, you need to run:
systemctl reload apache2
Step 17: Enable the read write module of apache
root@linuxhelp:~# a2enmod rewrite
Enabling module rewrite.
To activate the new configura``tion, you need to run:
systemctl restart apache2
Step 18: Configure omeka CMS database in the following file
root@linuxhelp:~# vi /var/www/omeka/config/database.ini
Step 19: Restart the apache webserver
root@linuxhelp:~# systemctl restart apache2
Step 20: Make host entry for omeks CMS
root@linuxhelp:~# vi /etc/hosts
192.168.6.115 www.linuxhelp1.com
Step 21: Ping server name in browser

Step 22: Configure the Admin credentials

Step 23: Login via Admin panel

Step 24: Admin Dashboard of omeka CMS

with this installation and configuration of omeka CMS on ubuntu 21.04 comes to an end
Comments ( 0 )
No comments available