Upgrading to ME 1.25

Elentra ME 1.25 was released on April 4th, 2023.

Release 1.27 introduced breaking changes to EJS 2. If you are using a version of Elentra that is 1.26.0 or less, you need to update deploy.php to ensure "branch_ejs" is pointing to "v2.6.0"

Important Upgrade Notes

Elentra ME 1.25 requires PHP 8, and uses Laravel 9.

Please review the Important Changes section before proceeding.

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 [e-mail]: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-pre-1240) 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.25 and click Pull consortium/release/1.25 into uni/staging. Alternatively, pull the latest stable release tag, e.g. v1.25.2. 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.

We recommend against pushing your changes to your origin remote at this point. Please wait until Part 2 has been completed and you have finished some initial testing on your local developer environment.

Release branches (e.g. release/1.25) usually only get bug fixes and have low potential risk, but issues may not be identified until our integration testing before the next release. Therefore, release branches are not completely stable. Release tags (e.g. v1.25.2), on the other hand, are NEVER actively worked on and are the official minor release for a given major release, because tags are only created from the release/1.x branches AFTER our integration testing has passed.

Updating a Branded Edition Elentra API

If your institution does not have a Branded Edition Elentra API, skip this section entirely. These instructions are only applicable to installations of Elentra that have a Branded Edition Elentra API. Not sure? Please contact the Elentra Consortium Core Team for assistance.

1. To update your Branded Edition Elentra API, first clone or checkout the compatible version of your Branded Edition Elentra API to your local environment using a git tool like Sourcetree. To find the required version, please consult the Compatibility Matrix.
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 the identified branch from step 1 (i.e. compatible version listed in Compatibility Matrix) and click Pull consortium/<branch> into <Deployed Branch>. 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 v8.0.0 and the composer.json provided with Elentra ME 1.25 specifies that the major version of API version must be ~8.0. Create a new tag where the current date follows the patch version: 8.0.1.20230406. More information about tagging API releases can be found here.
6. Finally, ensure that within your new Deployer deployment recipe (deploy.php) to set the enabled_branded_api option to true and the deployment script will take care of the rest during deployment.

Part 2: Settings and Branding Update

During every major Elentra ME version upgrade, you are required to compare:

1. The stock settings.inc.php file with each environmental settings file in use.

2. The www-root/templates/default template directory with each Branded Edition customized template within the www-root/templates directory.

Failure to compare and update all environmental settings files and customized templates could result in a non-functional or semi-functional installation of Elentra ME. If you have questions or require assistance, please contact the Elentra Consortium Core Team.

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.

At this point, providing you're satisfied with your local testing, we would recommend that you push your changes to your origin remote.

Part 4: Configuring Deployer

Elentra ME 1.25 requires Deployer v6.8.0 in order to support the new requirement of a local build step for Elentra JS 2. If you already have Deployer configured, you can skip this step.

The full Elentra Deployment Tool documentation is available from within the Elentra Deployment documentation section.

The following transition instructions are to be used as reference-only, as there may be unique circumstances within your existing deployment recipe to be considered.

Step 1: Copy Deployer template files into your Branded Edition repository

Copy the .deployignore and deploy.php files from the Elentra Developer GitHub Repository and place them in your ~/Sites/uni-elentra-1x-me/deployment directory

Step 2: Update the values in the Deployer recipe template

Open the Deployer deployment/deploy.php deployment recipes in your editor. 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.

Variable Name	Description
application	Application Name (e.g., uni-elentra-1x-me)
packagist_token	Institutional Packagist.com Composer token
repository	Branded Edition Elentra ME Git repository location
branch	The default deployment branch (e.g., master) within your Branded Edition Elentra ME Git repository. This value is always overridden by the host configuration section (if present), so it not overly important.
repository_ejs	Default recommended. This can be left as-is unless you have a Branded Edition Elentra JS Git repository.
branch_ejs	Default recommended. This can be left as-in unless you have a Branded Edition Elentra JS Git repository. This value is always overridden by the host configuration section (if present), so it not overly important.
enable_branded_api	Default value is false. If you have a Branded Edition Elentra API with your implementation of Elentra then please set this to true

Once you have configured all of the variables correctly, the next step is to translate the hosts configuration. The following section illustrates a single staging server and multiple production server transition.

For more documentation related to host configuration options, please see the Deployer Hosts documentation, which is quite extensive.

Example Deployer (deploy.php) Recipe Host configuration

# 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();

Step 3: Review Deployment Commands

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.

The Deployer deployment strategy transition should require no Apache configuration changes and was designed to be fully backwards compatible with older Capistrano recipes.

Deployer	Capistrano
dep deploy staging	cap staging deploy
dep deploy production	cap production deploy
dep rollback staging	cap staging deploy:rollback

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 navigate 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.

For the most accurate review possible, we would recommend that you have a recent version of your production databases installed and scrubbed loaded on your staging database server. This is typically achieved using the scrub.sh shell script included with the Elentra Platform.

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 verify that you are now running the latest version of Elentra ME.

Important Changes

PHP 8.0

• When you upgrade your version of PHP to 8.0, you will need to test your customizations to make sure they are compatible with PHP 8.0.

• PHP 7.4 is no longer supported.

• Backward Incompatible Changes in PHP 8.0: https://www.php.net/manual/en/migration80.incompatible.php

Laravel 9

This release upgrades the Laravel version used by the core code base from Laravel 6.x to 9.x.

In order to help upgrade your customizations to be compatible with Laravel 9.x, do the following:

1. Ensure that you are merging our updates to the composer.json, and that the composer.lock is updated as well.

2. If you have a branded API, update your customizations to make them compatible with Laravel 9.x.

   • To this end, it may be useful to purchase Laravel Shift to to automatically update your API code base to be compatible.
   • The cost is about $30 CAD per version upgrade i.e. 6.x to 7.x, 7.x to 8.x, and 8.x to 9.x.

   • The service will generate pull requests to your branded API repository that will fix lines of code incompatible with the new version.

3. Test all of your customizations to ensure that they still work with Laravel 9.x.

Composer v2

Composer v1 is no longer supported. In elentra-1x-me/deployment/deploy.php, change the follow line:

    run('curl -sS https://getcomposer.org/installer | php -- --install-dir={{release_path}} --version=1.10.16', ['timeout' => null]);

to:

    run('curl -sS https://getcomposer.org/installer | php -- --install-dir={{release_path}} --version=2.6.2', ['timeout' => null]);

i.e. change it from version=1.10.16 to version=2.6.2.