I checked out your edit and what’s going on is pretty weird. my recommendation (if you don’t wanna just use the native import/export feature and give up on DB dumps) is to (on the new server) create a minimal tandoor docker-compose.yml, run it, do minimal setup, see if it works, and if the fresh container works, check the permissions, then just replicate those perms for your other postgres directory that contains data you actually care about. good luck!
agreed, good find with that import/export feature, didn’t think to check for that since I don’t use tandoor. personally I’d just use the native import/export feature though since it feels less hacky than copying the whole DB imo. but if OP still wants to copy the files over, it might be easier to either just tar or tar + gzip rather than tar + zip so they can do it all in one command.
you’re probably right about it being a permissions error but also including some relevant logs would be useful (or just stick all of them on pastebin or something and give us a link). could also be a docker misconfiguration considering it’s a different system and I assume they’re not identically set up with Ansible or something similar
edit: also id personally use tar because I’m not entirely sure zip files preserve linux permissions
edit again: from 2 seconds of google searches, I think I’m correct about that, so definitely try using tar
afaik it doesn’t support any notifs yet so report notifications will probably be added at the same time as general notification functionality.
honestly I don’t think it’s really a significant issue but if you’re worried just use a fs that can repair itself like zfs (not sure if btrfs can do that too but it might)
not sure where you are but in the US I see a lot of cheap used laptops being sold online with broken screens for example or messed up keyboard/touchpad, etc. stuff that would make it awful for use as a laptop but almost entirely unimportant for a server use-case (if the kb/touchpad is dead you can just plug in an external during initial setup/troubleshooting). of course you gotta make sure that it wasn’t damaged in a way that would matter more. ex: if the kb/touchpad are broken due to water damage I’d be wary of issues with other vital parts
it’s a single comment from a single bot that you can block. it’s probably useful for new people, there’s always mountains of acronyms in tech
try logging in via username rather than email or the opposite depending on what you’ve tried. thats the only issue I’ve had with logging in
I doubt you’re being serious but I was curious and did the math. transferring 88000 TB over a 1Gbps connection would take 8148 days or over 22 years straight
sorry! didn’t get a notification for this. but I’m liking lemm.ee because the instance is extremely well run and hasn’t had any noticable downtime or performance issues I’ve noticed with others. the person who runs it seems to really know what they’re doing and IIRC they’re a Lemmy dev.
“alternatively obtained” is funny but yea I completely agree. also makes the project description much less clunky sounding and more descriptive.
best time to make that decision is the present. personally I just transferred over my subscriptions and deleted the account of the previous instance I was on. it didn’t take much time.
yup, this is what I do and it works great. just be careful if you add plugins that store a ton of metadata that changes a lot (or logs) because that can lead to some sync conflicts and you might wanna exclude them. I’ve just been ignoring the sync conflicts tho and haven’t had issues yet so maybe you could do the same