Yes, more control over what happens between server/client. Sorry, that wasnt clear.

Immich aims to be a google photos replacement, which has this function built in.

Now, I don’t care if it works only one way, but it should be clear.

I love immich. I just wish for two things:

• synchronised deletes on client server
• the edit tools on mobile to actually work on the photo at hand instead of creating a new photo with new metadata. May as well not have the tools, tbh.

I would argue that logrotate was the ABC of any sysadmin in 2005, but today that should be a solved problem, whether in docker or bare metal.

I don’t disagree that logrotate is a sensible answer here, but making that the responsibility of the user is silly.

deleted by creator

deleted by creator

Although I have my issues with plex, jellyfin has its own problems:

• STILL can’t clear out the TS transcoded files automatically. So if you watch a bunch of TV episodes on a weekend, your jellyfin container will run out of space and break.
• STILL can’t handle subtitles properly. I swear, this must be jellyfin’s Waterloo.
• jellyfin cannot demux 5.1 and present stereo sound on certain streams. I think this is a tooling issue. But it’s low level enough that I can handle it manually with mkvtoolnix myself on the few cases it happens.

I use individual lxc for each docker compose so I don’t have to revert 8 services at once if I need to restore.

I would also argue that an alpine lxc runs in 22mb ram by itself … Significantly smaller footprint on disk and in memory. But most importantly, lxc can actually share memory space effectively, one doesn’t need to reserve blocks of ram.