INFRA-517 Part 1: Update Matomo Version #22
Conversation
Why these changes are being made: This is a documentation update, based on some experiementation in the Dev1 instance of Matomo. The How-To walks through the general plan for deploying a new premium plugin that requires a license key.
Why these changes are being made: Before proceeding with the installation of the new premium plugins, we update the instance of Matomo to the latest Docker version: 5.3.1 How this change is implemented: * Updat the Dockerfile with the latest container source. Related Jira tickets: * https://mitlibraries.atlassian.net/browse/INFRA-517
Why these changes are being made: This is required to be able to install premium license keys. During the testing in Dev1, it quickly became clear that the Marketplace plugin must be active to manage the premium license keys. How this is implemented: * Add the Marketplace plugin to the [Plugins] section of the config.ini.php file.
|
@dhrutibc I don't need your official approval on this, but I tagged you as a reviewer mostly to keep you in the loop. When this gets approved and merged to |
vab
left a comment
vab
left a comment
There was a problem hiding this comment.
lgtm.
Wow... the licence key model they are using is a pain.
Looking through all this, I noticed we are on the last supported version of MariaDB for RDS. I saw you were working on the Blue-Green deployments. I think we should go up to a recent version of MariaDB version very soon. I think we should go all the way up to v11.4 (most recent on AWS). Motomo had an odd compatibility issue with v11.5 (not available on AWS, yet). But, they fixed that back in Motomo v5.1.2. If we don't get off v10.5, AWS may force us to v10.6 or v10.11 soon, unexpectedly.
Indeed!!
Yup. After enabling the blue/green in the mitlib-tf-workloads-matomo repo, I did update the MariaDB database version to 10.5.27, so we are okay for the time being. But, I agree that we should get to 11.x by the summer. |
What does this PR do?
Helpful background context
See NFRA-517 (link below) for more details of the request. The the new How-To file that is part of this PR for details on why this PR is happening and what the next steps are.
In summary, we need to do multiple passes through this repository to enable a new premium plugin. This pass handles the update to Matomo (to 5.3.1) and the enabling of the Marketplace plugin (so that we can use premium license keys). Once this has moved through to prod (e.g., a tagged release), we will push through the next round of changes to deploy the new premium plugins.
How can a reviewer manually see the effects of these changes?
Once this is deployed to Dev1 (as part of creating this PR), an user with "superuser" privileges can log in to the Matomo UI and
Includes new or updated dependencies?
NO
What are the relevant tickets?
Developer
Code Reviewer
(not just this pull request message)