Skip to content

INFRA-517 Part 1: Update Matomo Version #22

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 3 commits into from
Apr 24, 2025
Merged

INFRA-517 Part 1: Update Matomo Version #22

merged 3 commits into from
Apr 24, 2025

Conversation

cabutlermit
Copy link
Contributor

@cabutlermit cabutlermit commented Apr 22, 2025 •
edited by vab
Loading

What does this PR do?

  1. Add documentation for premium plugin installation.
  2. Update Matomo to 5.3.1
  3. Enable the Marketplace plugin

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

  1. Verify that the installed version is 5.3.1
  2. Verify that the Marketplace plugin is active.

Includes new or updated dependencies?

NO

What are the relevant tickets?

Developer

  • [n/a] All new ENV is documented in README (or there is none)
  • Stakeholder approval has been confirmed (or is not needed)

Code Reviewer

  • The commit message is clear and follows our guidelines
    (not just this pull request message)
  • There are appropriate tests covering any new functionality
  • The documentation has been updated or is unnecessary
  • The changes have been verified
  • New dependencies are appropriate or there were no changes

@cabutlermit
Documentation for Premium Plugins
b9e49cc 
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.
@cabutlermit
Upgrade to Matomo 5.3.1
edbcfa3 
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
@cabutlermit
Enable Marketplace Plugin
24f9913 
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.
@cabutlermit cabutlermit marked this pull request as ready for review April 24, 2025 14:44
@cabutlermit cabutlermit requested a review from a team as a code owner April 24, 2025 14:44
@cabutlermit cabutlermit requested a review from dhrutibc April 24, 2025 14:44
@cabutlermit
Copy link
Contributor Author

@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 main it will update the matomo-stage service to 5.3.1 and enable the Marketplace app. Definitely take a minute or two to read the [docs/HowTos/HOWTO-premium-plugins.md] for details on the steps to install and activate the premium features.

vab
vab approved these changes Apr 24, 2025
View reviewed changes
Copy link
Contributor

@vab vab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@cabutlermit
Copy link
Contributor Author

Wow... the licence key model they are using is a pain.

Indeed!!

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.

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.

@cabutlermit cabutlermit merged commit 8c2d2df into main Apr 24, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@vab vab vab approved these changes

@dhrutibc dhrutibc Awaiting requested review from dhrutibc

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@cabutlermit @vab