Self-Hosted: provide migration guide to help move from native to kubernetes #89
Conversation
| kubectl scale statefulset postgres --replicas 0 -n default | ||
| kubectl delete pvc postgres-data-postgres-0 -n default | ||
| kubectl scale statefulset postgres --replicas 1 -n default | ||
| cat packagist_db.sql | kubectl exec -it -n default statefulsets/postgres -- psql -U postgres -d packagist_db |
There was a problem hiding this comment.
Pretty tricky to review this now. Cause based on the conversation we had yesterday, we need to explain a lot about kubectl and/or how to verify that the commands worked?
Doesnt this need a bit time to scale up and down? in practice?
|
So for the generic redis import, I would suggest following: a) lets see how many will use their external redis? maybe this doesnt need to go fully into the guide, just a note to contact us, when they need that? |
… where to wait for up/down scaling
| ## Backing up the data | ||
|
|
||
| Private Packagist Self-Hosted uses three different storages. A PostgreSQL database used as primary storage, | ||
| a Redis database used as secondary storage, cache, and job queue, and a file/blob storage for uploaded artifacts and dist |
There was a problem hiding this comment.
secondary storage? That suggests like it's only used as a cache?
There was a problem hiding this comment.
How so? Secondary storage doesn't mean cache?
There was a problem hiding this comment.
Secondary to me suggests it stands behind the first. I don't really know what that means at all, backups? Would prefer that term would be replaced with something more concrete.
Co-authored-by: Nils Adermann <n.adermann@packagist.com>
Co-authored-by: Philipp Scheit <p.scheit@packagist.com> Co-authored-by: Nils Adermann <n.adermann@packagist.com>
This is still missing a generic Redis import solution