-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Shut down staging deployment #45
Comments
This was referenced Mar 28, 2023
Mr0grog
added a commit
to edgi-govdata-archiving/web-monitoring-db
that referenced
this issue
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-db
that referenced
this issue
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).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As part of edgi-govdata-archiving/web-monitoring#168, there’s no reason to keep the staging deployment around if we are no longer doing active development, and we should shut it down (and shrink the number of nodes allocated to the cluster).
The text was updated successfully, but these errors were encountered: