Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Develop a test and deploy workflow #11

Open
hortongn opened this issue Aug 27, 2021 · 4 comments
Open

Develop a test and deploy workflow #11

hortongn opened this issue Aug 27, 2021 · 4 comments
Labels
CM blocker Good for newcomers
Milestone

Comments

@hortongn
Copy link
Member

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 hortongn added this to the Production milestone Aug 27, 2021
@hortongn hortongn added the CM blocker Good for newcomers label Aug 27, 2021
@hortongn hortongn mentioned this issue Sep 15, 2021
4 tasks
@hortongn
Copy link
Member Author

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

@hortongn
Copy link
Member Author

hortongn commented Sep 23, 2021

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:
    [email protected]
    [email protected]
  • 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

Notify the team
Mark the change successful

@hortongn
Copy link
Member Author

hortongn commented Sep 28, 2021

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
Copy link
Member Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CM blocker Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant