Develop a test and deploy workflow

[hortongn]

Install modules, themes, other changes to libappstest Verify it works Commit to Github Deploy repo to production Deploying config files and any other secrets

[hortongn]

Deploy new instance on libappstest:

Porthos

• mysql -u root -p
• mysql> create database omeka_s_temp;
• mysql> grant all on omeka_s_temp.* to 'omeka_temp'@'libappstest.libraries.uc.edu' identified by '****';
• mysql> flush privileges;
• mysql> exit;

libappstest

• sudo -s
• cd /var/www
• git clone https://github.com/uclibs/omeka-s.git omekas-temp
• cd omekas-temp
• git checkout production
• cd ..
• chown -R apache:apache omekas-temp
• create /var/www/html/Connections/omekas-temp-database.ini
• cd /var/www/omekas-temp/config
• ln -s /var/www/html/Connections/omekas-temp-database.ini database.ini
• Create /var/httpd/conf.d/omeka-s.conf
• systemctl httpd restart

Omeka web app

• visit https://libappstest.libraries.uc.edu/sitestemp
• create the first user
• Customize settings, modules, etc.

[hortongn]

Deploy to production:

ssh libitdb2.libraries.uc.edu

• mysql -u root -p
• mysql> create database omekas;
• mysql> grant all on omekas.* to 'omekas'@'libapps.libraries.uc.edu' identified by '****'; ** note had to add grant all to the following in addition to libapps.libraries.uc.edu: -omekas@illiad.uc.edu -omekas@libitdb2.libraries.uc.edu
• mysql> flush privileges;
• mysql> exit;

ssh libapps.libraries.uc.edu

• sudo -s

• cd /var/www

• git clone https://github.com/uclibs/omeka-s.git omekas

• cd omekas

• git checkout production

• cd ..

• chown -R apache:apache omekas

• create /var/www/html/Connections/omekas-database.ini user = "omekas" password = "***" dbname = "omekas" host = "libitdb2.libraries.uc.edu" ;port = ;;unix_socket = ;;log_path =

• cd /var/www/omekas/config

• ln -s /var/www/html/Connections/omekas-database.ini database.ini

• Create /etc/httpd/conf.d/omekas.conf Alias /sites "/var/www/omekas" <Directory "/var/www/omekas"> Options Indexes FollowSymLinks AllowOverride All Require all granted

• systemctl restart httpd

Omeka web app

• visit https://libapps.libraries.uc.edu/sites
• create the first user
• Customize settings, modules, etc.

Notify the team Mark the change successful

[hortongn]

Application workflow draft

On libappstest (qa branch)

• git checkout qa
• git pull (to make sure we're starting with the current qa branch)
• make our Omeka (file) changes
• Verify the changes work
• Commit change to git
• Push changes up to github

Change Management

• Submit a change request
• Get request approved

On libapps (production branch)

• git pull
• git merge qa
• Activate any new themes, mdoules, etc.
• Verify everything works

marking the change request successful

[hortongn]

Content workflow draft

Site content can be created and edited directly on production without change requests Site setup ???

Should each site have an accessibility check?