Skip to content
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.

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

Set up good_job for ActiveJob backend #1097

Merged
merged 4 commits into from
Mar 29, 2023

Conversation

Mr0grog
Copy link
Member

@Mr0grog Mr0grog commented Mar 29, 2023

As part of slimming down the production cluster (edgi-govdata-archiving/web-monitoring-ops#45), we can use good_job to do our job queuing in Postgres rather than running a Redis instance (we still use Redis as a cache, but that is outside the cluster).

As part of slimming down the production cluster, we can use good_job to do our job queuing in Postgres rather than running a Redis instance (we still use Redis as a cache, but that is outside the cluster).
This is no longer used and no longer relevant!
@Mr0grog Mr0grog merged commit 4c1c0f6 into main Mar 29, 2023
@Mr0grog Mr0grog deleted the reque-is-expensive-lets-pack-it-into-postgres branch March 29, 2023 00:13
Mr0grog added a commit that referenced this pull request Mar 29, 2023
As part of slimming down the production cluster (edgi-govdata-archiving/web-monitoring-ops#45), we can use good_job to do our job queuing in Postgres rather than running a Redis instance (we still use Redis as a cache, but that is outside the cluster).
Mr0grog added a commit to edgi-govdata-archiving/web-monitoring-ops that referenced this pull request Mar 29, 2023
We should remove the Redis deployments and services from the cluster after this successfully runs a daily import job in a few hours (or deal with whatever breaks!).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant