Upgrade Instructions

Part 1: Source Code Update

1. From within Sourcetree on your developer workstation, open your existing local Elentra ME Branded Edition (i.e., uni-elentra-1x-me) repository.

2. If you do not currently have a consortium Git remote that points to the Consortium Edition elentra-1x-me repository, then ensure that you add one:

   git remote add consortium git@github.com:ElentraProject/elentra-1x-me.git

3. Click the "Fetch" button (ensuring that "Fetch from all remotes" and "Prune tracking branches no longer present on remote(s)" options are checked) or type git fetch consortium.

4. Checkout your Branded Edition staging branch (e.g., uni/staging) and create a new branch based on this branch (e.g., uni/staging-v118) just for easy restore purposes in case it's needed. Once that branch has been created, checkout the original Branded Edition staging branch (e.g., uni/staging) and continue.

5. Within the "Remotes" section in Sourcetree sidebar, expand the consortium remote, then right click on release/1.19 and click Pull consortium/release/1.19 into uni/staging. At this point, you may be asked to resolve any merge conflicts that have been created by making modifications to your Branded Edition that conflict with changes that have been made to the Consortium Edition. Depending on your level of conflict, this could be as simple as a minor modification to the composer.lock file or something much more complex. If you require assistance, please book an appointment with the Elentra Consortium Core Team, or chat with us on Slack in the #developers channel and we will provide you with guidance or assistance on moving forward. Generally speaking, we always recommend that Consortium Participants follow the Contribution best practices defined in our documentation, which may help reduce the number of conflicts that you encounter.

6. Once the merge conflicts have been resolved, commit the merge to your uni/staging branch and continue to Part 2 of the instructions.

Updating a Branded Edition Elentra API

1. To update your Branded Edition Elentra API, first clone or checkout the master branch of your Branded Edition Elentra API to your local environment using Sourcetree.

2. Click the "Fetch" button (ensuring that "Fetch from all remotes" and "Prune tracking branches no longer present on remote(s)" options are checked) or type git fetch consortium.

3. Within the "Remotes" section in Sourcetree sidebar, expand the consortium remote, then right click on master and click Pull consortium/master into uni/master. There may be merge conflicts that must be resolved if customizations made to your Branded Edition Elentra API.

4. Resolve any merge conflicts and commit the changes to the master branch of your Branded Edition Elentra API. Push these changes to your origin remote.

5. Using Sourcetree, create a new tag that follows semantic versioning. For example at the time of writing, the latest tagged release of the api is v4.1.3 and the composer.json provided with Elentra ME 1.19 specifies that the major version of API version must be ~4.0. Create a new tag where the current date follows the patch version: 4.1.3.20200827. More information about tagging API releases can be found here.

6. Finally, ensure that within your new Deployer deployment recipe (deploy.php) that you set theenabled_branded_api option to true and the deployment script will take care of the rest during deployment.

Part 2: Settings and Branding Update

1. Using a tool like Araxis Merge or Meld, compare www-root/core/config/settings.inc.php with each environmental settings file in the www-root/core/config directory (e.g., settings-staging.inc.php, settings-production.inc.php). When you compare the Consortium Edition settings.inc.php file with your Branded Edition files, you are looking to add additional settings that have been added to the stock settings.inc.php file and remove any settings that have been removed from the stock settings.inc.php file. In most cases, your Branded Edition settings files should have the same lines (albeit potentially different settings values) as the Consortium Edition. Once you have compared your settings files, commit the changes to your uni/staging branch.

2. Using a tool like Araxis Merge or Meld, compare the www-root/templates/default directory with each Branded Edition customized template in the www-root/templates directory (e.g., www-root/templates/uni). In most cases, you will want to add missing files, update your language files, examine each modification to the CSS files, and add any modifications to your header.tpl.php files. This process can take some time depending on the level of change in your implementation, and should be repeated for each template you have created. Once you have compared your templates, commit the changes to your uni/staging branch.

Part 3: Testing Locally

Now that you have upgraded your source code and updated your settings and templates. You should begin reviewing and testing the upgrade on your developer workstation. Before testing can begin we need to do a few things.

1. Log into your local elentra-developer Docker container, and change to your uni-elentra-1x-me directory:

   docker exec -it elentra-developer bash
   cd /var/www/vhosts/uni-elentra-1x-me

2. Ensure that the latest Composer dependencies installed:

   composer install

3. Ensure that the database migrations are completed:

   php elentra migrate --up

4. Providing these steps were successful, you should now be able to visit https://uni-elentra-1x-me.localhost in your web browser and being your local upgrade review.

Part 4: Updating Deployment Strategy

Part 4 / Step 1: Copy Deployer template files into your Branded Edition repository.

Download the raw .deployignore and deploy.php files from the Elentra Developer GitHub Repository and place them in your ~/Sites/uni-elentra-1x-me/deployment directory alongside the existing Capistrano Capfile and config/deploy.rb files in the uni/staging branch.

Part 4 / Step 2: Update the Deployer recipe template with actual values.

Open both the Capistrano ("Cap") deployment/config/deploy.rb and the Deployer ("Dep") deployment/deploy.php deployment recipes in your editor or IDE. There are a few variables at the top of deploy.php that need to be set. The following table describes variable names that must set.

Once you have set all of the variable names correctly in comparison with the Capistrano recipe, the next step is to translate the hosts configuration. The following section illustrates a single staging server and multiple production server transition.

Example Capistrano (deploy.rb) Recipe

# Elentra ME
task :staging do
  server "elentra-staging.med.university.edu", :app, :web, :db, :primary => true
​
  set :user, "staging"
​
  set :branch, "uni/staging"
  set :environment, "staging"
  set :deploy_to, "/var/www/vhosts/elentra-staging.med.university.edu"
end
task :production do
  server "elentra01.med.university.edu", :app, :web, :primary => true
  server "elentra02.med.university.edu", :app, :web
​
  set :user, "production"
​
  set :branch, "uni/production"
  set :environment, "production"
  set :deploy_to, "/var/www/vhosts/elentra.med.university.edu"
end

Example Deployer (deploy.php) Recipe

# Elentra ME
​
// Staging Server
host('elentra-staging.med.university.edu')
    ->stage('staging')
    ->user('staging')
    ->set('branch', 'uni/staging')
    ->set('branch_ejs', 'develop')
    ->set('deploy_path', '/var/www/vhosts/elentra-staging.med.university.edu')
    ->roles('app')
    ->forwardAgent();
​
// Production Server
host('elentra01.med.university.edu', 'elentra02.med.university.edu')
    ->stage('production')
    ->user('production')
    ->set('branch', 'uni/production')
    ->set('branch_ejs', 'master')
    ->set('deploy_path', '/var/www/vhosts/elentra.med.university.edu')
    ->roles('app')
    ->forwardAgent();

Part 4 / Step 3: Review the deployment command crosswalk.

The typical deployment commands used by institutions are referenced below, but please see the Elentra Deployment documentation for a full list of all commands available.

Part 5: Testing on Staging

Providing that you have pushed the changes to your uni/staging branch to your origin remote, you can now deploy the upgrade to your staging environment from within your Docker container.

1. Log into your local elentra-developer Docker container, and change to your deployment directory:

   docker exec -it elentra-developer bash
   cd /var/www/vhosts/uni-elentra-1x-me/deployment

2. Deploy changes to your staging server using the new Deployer deployment recipe:

   dep deploy staging

3. Providing the deployment was successful, you should now be able to visit https://elentra-staging.med.university.edu in your web browser to begin a thorough review of your upgraded Branded Edition implementation of Elentra ME.

Part 6: Deploy to Production

Providing that you have thoroughly tested your upgraded Branded Edition implementation of Elentra ME on within your staging environment, it is safe to proceed with a production upgrade.

1. From within Sourcetree on your developer workstation, open your existing local Elentra ME Branded Edition (i.e., uni-elentra-1x-me) repository.

2. Checkout your uni/production branch.

3. Right click on your uni/staging branch and click "Merge uni/staging into uni/production". This will merge all of the commits that have gone into creating the upgrade, into your uni/production branch.

4. Push the commits in the uni/production branch to your origin remote. Log into your local elentra-developer Docker container, and change to your deployment directory:

   docker exec -it elentra-developer bash
   cd /var/www/vhosts/uni-elentra-1x-me/deployment

5. Deploy changes to your production server using the new Deployer deployment recipe:

   dep deploy production

6. Providing the deployment was successful, you should now be able to visit https://elentra.med.university.edu in your web browser and enjoy the fact that you are now running the latest version of Elentra ME.

​