Remove Matomo API tracking code and Celery task queue #820
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…seems to have some breaking configuration changes currently. I'll cherry pick this commit into it's own pull request if this works.
… tracking. Still need to remove server starting of proc-celery and db tables and auth_token from ssm.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #728 and #757 .
This gets rid of API tracking code and also removes Celery task queue and SQLAlchemy (required by Celery).
Things to do after deploy: remove Celery DB tables manually and remove the token for Matomo from SSM which isn't used anymore.
I already checked with Ashley and she removed the startup of the service/daemon for Celery on stage/production. 🎉
Also we can archive the forked repo on github.