Open CakePost opened 1 week ago
This should be a proposal rather than a bug. And I don't know whether it's possible to recover packages from disk.
Thanks @lunny I wanted to make this a type/question
as I wasn't sure if something like this was even implemented.
Description
A few days ago I encountered an issue with the postgres database I was using for our Gitea instance. I documented the events that caused the corruption of our database on serverfault in the hopes of being able to recover it, though that's looking unlikely.
I'm now facing the process of recovering our instance to the best of my ability. Using the "adopt repository" feature a lot of the stress is mitigated as I can just have users remake their accounts (of which there are only 30) and then relink their repositories. However, a few users have been using packages and I'd like to also be able to restore those as well.
Wiping the corrupted database (after a backup of course) and starting fresh, an execution of the
gitea doctor
shows this:Of course running
gitea doctor check --all --fix
just deletes anything that's orphaned. What I'd like to do is be able to re-associate all of the orphaned packages back with the accounts that made them.I do not know if this is something that can be done through the interface somewhere I'm missing, or if it can be done through the command line. Before I start having people re-onboarded onto the server, I'd like to know what I can do to get their packages back onto their accounts.
Gitea Version
1.21.6
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
While the repository section in the site administration panel provides a really easy way to re-associate repos with their users (once recreating their accounts), the package code assets do not seem to have this option.
Git Version
2.30.2
Operating System
Debian GNU/Linux 11 (bullseye)
How are you running Gitea?
I am running gitea in a docker container using the following docker compose config.
Database
PostgreSQL