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

downsize ecamp3-staging postgres DB back to 1GB RAM instance #5696

Closed
BacLuc opened this issue Aug 12, 2024 · 1 comment
Closed

downsize ecamp3-staging postgres DB back to 1GB RAM instance #5696

BacLuc opened this issue Aug 12, 2024 · 1 comment
Assignees

Comments

@BacLuc
Copy link
Contributor

BacLuc commented Aug 12, 2024

Most likely by deleting the staging DB cluster and setting it up again.

The goal is to reduce the costs for the db instance. (and to have the same setup as in prod agani)

⚠️ you need to restore a prod snapshot again.
This takes now some time because we now have quite some data in the db.
And

is not yet fixed.
After restoring, you need to deploy again, and run the script for the interesting camps manually.
While doing this, you can also collect

Only for @ecamp/core members

@BacLuc BacLuc self-assigned this Nov 2, 2024
@BacLuc BacLuc moved this to In Progress in Development Kanban Nov 2, 2024
@BacLuc BacLuc closed this as completed Nov 2, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Done in Development Kanban Nov 2, 2024
@BacLuc BacLuc reopened this Nov 2, 2024
@BacLuc
Copy link
Contributor Author

BacLuc commented Nov 2, 2024

Done.
I did not have to set up the database again. I could fork it 2 times.
I also decreased the storage size to 10 GB like in prod.

@BacLuc BacLuc closed this as completed Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant