Fortunately I didn't loose any actual data.
So now I have 40GBs of useless objects because the data necessary to rebuild files from objects are gone with the database
Basically what happened is that I renamed the folder where my nextcloud docker-compose.yml is. Then I did docker-compose up -d which means that the postgres container created new volume since I did not use named volumes.
This wouldn't be so bad since the old volume was still there, just not attached to any container.
But then I run docker volume prune
I don't have a backup. Other than a snapshot of the entire vm
Hmm... not my thing
Makers, Don't Let Yourself Be Forced Into the 'Manager Schedule' https://blog.nuclino.com/makers-don-t-let-yourself-be-forced-into-the-manager-schedule
His call was cut. He's silent now. Good.
but instead of cameraConfigHolderBuilder we have camera_config_holder_builder because the former is "unpythonic"
Providers, Singletons, Factories, Builders we've got it all
I write shitty Python scripts
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!