

I’ve tried first removing the -it
flag as suggested by @farcaller@fstab.sh in another comment and see if that works out.
Otherwise I’ll try to debug with a logfile as you suggested, thanks!
I’ve tried first removing the -it
flag as suggested by @farcaller@fstab.sh in another comment and see if that works out.
Otherwise I’ll try to debug with a logfile as you suggested, thanks!
Oh you are right, thank you. I’ve tried removing it and see if it fixes the issue 🤞
Thank you for pointing it out. I’ll fix it as soon as possible and see if it solves the issue.
However, the script I pasted is fired by another script (called docker_backupper.sh
, that is the one triggered by the cronjob and whose purpose is firing a specific script for each service to be backed up) and that script has the on top, so I fear adding it also to the “invoked scripts” won’t change that much
But if the atproto team actually releases a way to selfhost a relay server as well (and not just a data server), in theory if bluesky enshittifies you could always fork the app, selfhost your PDS and Relay and migrate, while still being able to interact with the people in the “mainstream bluesky”.
I know this is a big if, and that at the moment it’s not reality, but the Atmosphere it’s at leaat 10 years younger than the Fediverse. So I’d say let’s not call it shit yet and just see how it evolves…
Anyone willing to summarize those mistakes here, for those who can’t watch the video rn?
IT WORKED! Thank yoy again for the help :)