Closed hikari-no-yume closed 1 year ago
Maybe related to https://github.com/superseriousbusiness/gotosocial/issues/1645? I'm using SQLite though.
Ah, doing media pruning through the web interface seems to have worked. :)
So it's just a CLI issue.
Pruning works fine despite the error; it just looks a little grungy. What happened is you ran a dry run, which only counts how many media items you will prune and takes no other action.
Dry run is the default, you need --dry-run=false
to actually prune from CLI. It'll still barf up that cache spindown error but it'll work.
There is a bug here that that error appears at all, but yeah CLI prunes should work.
Ohh, I noticed the dry run warning but I was really confused because I hadn't passed the --dry-run
flag, which I assumed was what you use for dry runs. The documentation for that flag could be improved I guess.
Again (again) #1690 includes something which should help with this :)
Describe the bug with a clear and concise description of what the bug is.
GoToSocial is using a lot of disk space on my VPS. Until recently I was using 0.5.2, which didn't do sufficient pruning (AIUI). I upgraded to 0.8.1 and want to run the
admin media prune remote
command. However, it errors:What's your GoToSocial Version?
0.8.1
GoToSocial Arch
arm64 binary
What happened?
No response
What you expected to happen?
No response
How to reproduce it?
No response
Anything else we need to know?
No response