Made up spellings are bad, but good luck searching for anything that isn’t a made up spelling or two words put together.

I think versioning is the better option.

are you writing about losing the backUp drive?

No, losing your main version. Imagine you have a computer with syncthing and a server where it syncs to. If you chose no deletions, then it will sync all files to the server but all the stuff you deleted (draft documents, random files, photos from that time your kid held the camera button on your phone down and took 3000 photos in 30 seconds) will be deleted from your computer but still there on your server.

When you computer gets struck by lightning and everything is destroyed but the server is fine, now you have to re-sort out all your files because all the stuff you deleted is still on the server version.

Your suggestion of enabling the option to keep previous versions is probably cleaner. Personally I prefer to keep previous versions and deduplicate to save space.

Yes, if you go with something like syncthing, have it also sync to a server where you run borg backup so you get the incremental backup.

Yip you can do that but then it’s messy! And what if you overwrite a file by accident?

And if you do lose your hard drive then you have a weird state to restore from.

I’d much prefer the ability to restore to a point in time that comes with something like borg.

Remember sync isn’t a good backup. You’re thinking of loss of drives but if this is important data you need to also consider mistakes.

If you accidentally delete files you shouldn’t, you don’t want this deletion to sync to all your copies so it’s gone for good and the backup doesn’t help.

Personally I use borgmatic to keep incremental, deduplicated backups. Then I can go back to previous states.

If you install nextcloud all in one, it comes with a backup solution (also borg based). Then devices don’t need a copy of every file. But you’ll want your server to have a backup drive for this.

I then sync my borg backup to a backblaze b2 bucket for offsite, encrypted backup using rclone. That then meets the 3 2 1 backup plan.

I notice you mention Jellyfin. I don’t back up my Jellyfin media, the cloud storage for that could get very expensive and I could get it again if I needed it.

I think PieFed has only recently got an API for apps to connect to, hence the surge.

Many of the .ee communities are in the process of migrating, so hopefully the list can be updated with their new homes.

2 years for me as well!

Ok thanks, I’ll have to be extra careful deploying any changes.

Thanks! I did see there’s a docker format and a podman format which I assume is what this difference is about. I’m not against discord but I’ve never really used it. I’ll check it out if I get desperate 🙂

Thanks, I had already played a bit with distrobox and hadn’t worked that out either. It seems adding a Z flag to my bind mount to keep SELinux happy is all that was needed.

I seem to have got it working using podman, adding a Z flag to the bind mount to make SELinux happy.

Oh shit I think that’s it! I’ve added that Z flag to each bind mount declaration in compose.yaml, and it seems to be running properly now. Thanks!

Any idea what the implications are of this transferring to an ubuntu based distro?

As far as I can tell, you just run the command with sudo to run as root? But this doesn’t help, I have been using sudo.

Edit: I think this is solved, someone else mentioned using the Z flag on the bind mount declaration and it seems to be working!

I’m already using bind mounts under the /home directory. I learnt pretty early on day 1 not to fight the distro, so I’m trying to understand the way Bazzite wants this to be done. From another reply, it sounds like it’s a difference in rootless/rootful containers so I’m going to try to work out how to run a podman container as root and see if this helps.

Thanks, I will have a go at trying to get it running as a rootful container!

I was running Nobara before, which is also based on Fedora, so not sure why it would be different in regards to SELinux?

I mentioned this in my original post.

Searching online shows everyone saying just use podman, it comes pre-installed and is a drop in replacement. The problem is that it doesn’t work.

But someone else has mentioned the issue is the containers are rootless by default, so I’ll explore that line of troubleshooting.

I guess my position is that I am not worried about someone confirming content exists on my server. But I don’t live in the US, if I did I might be more worried. I also geofence to my country to limit exposure.

Cheers for that. Many of these issues allow an authenticated user to do admin actions if they do the right things, so it seems you should never allow a user that you don’t fully trust to have an account.

But outside of this, there isn’t anything in there that on its own worries me given the nature of the platform (that is, that if it all burnt down I could retrieve all data from other sources). I’m no expert but a cursory look shows a bunch of potential issues that may be layered with other issues but no clear attack path except with prior knowledge.

These should obviously be fixed but there’s nothing that makes me want to rip my server off the open internet in a hurry.