Jellyfin is a fork of Emby before they closed the code, so most likely everything you have on Emby you would have on Jellyfin but without the worry that tomorrow Emby will pull a Plex onto you. Up until a while ago they were so alike that you could use Emby client on a Jellyfin server, not sure if that’s still possible though.

I used to use Arch, now I use Nix, so that checks out

Not the person you’re asking, but I went the other way around like you, the main reason for me was that mealie can extract and import from plaintext, so it’s easier to migrate away if I ever want to. I rather have things closer to plaintext whenever possible.

I spent a while getting Ansible to be able to setup and maintain my server(s). And ended up not using it as much as I should, mostly because the computer I used to run Ansible from became a “Steam Machine” so I’m rarely sitting on it with a keyboard now and I don’t want to have personal info and keys on my work computer.

But it was a good learning, and useful while I used it. Now I just use ssh and compose files directly.

PiGallery is what you’re asking for, but you should consider Immich, it’s very simple to setup and you’ll get tons of features more that are extremely useful. I get you want something simple, but I don’t feel Immich is hard to setup or maintain, and it’s the difference between a simple photo gallery and google photos.

How much RAM does this use? And how is it different from Tinyauth or even Authelia?

Why do you want to expose them? This might limit the solutions.

The way I do this is in 2 different ways:

1. Tailscale, my server connects to tailscale so all I have to do is connect to it from my phone and I can access things remotely easily. This is the best for most things, but has the downside that others can’t access it as easily

2. I have a VPS (two actually at the moment as I’m switching providers from Vultr to IONOS) that also connects to tailscale so it can access my home server through it, then using Caddy I expose the services on a subdomain of the VPS. This is what I do for things that others might want to access, or things I don’t want to have to connect to tailscale to access.

If you’re going down the second route do consider that you will need to:

• Add something like fail2ban or crowdsec to the VPS as attacks will happen.
• Same reason you should add a dedicated authentication on front of most things. While I don’t expect the auth on services to be weak, it might be more vulnerable than a dedicated authentication service. You should look into Authelia, Authentik, or similar to put on front of your services so any attacker would first have to pass that to even get to your services.

I’m not a law expert, but I think even in Germany you would need to prove a pattern not a one off banned a black/trans person to accuse of discrimination. Otherwise any negative repercussion to a black/trans person would generate a discrimination lawsuit, and that just seems absurd.

I assume that if codeberg forces this it will do so with the most egregious offenders, because like you have pointed out it’s impossible to differentiate good code written with AI tools from good code written without them, but bad code written with AI tools is sometimes very differentiable from bad code written without them. And at the end of the day they’re trying to safe-guard against lawsuits over it (as the person uploading the code is not the owner) and becoming a slop repository.

But also, here’s the thing, they’re not making money of you hosting your code there, so it’s much harder to force them to take someone’s data. You could force Google to host your photos if you were unjustly banned, you can’t force me to do so if you found a loophole to use my server for that.

How would it be legally challengeable? No one can be legally forced to host someone else’s data against their will, that sounds ludicrous, otherwise people could sue YouTube for removing their videos before they were legally required to.

The TOS are essentially a way to let you know what they will consider, but legally they can remove your repo without any reason, they’re not legally required to host your data.

Echoing what others have said, Immich hasn’t had breaking changes in a while. That being said it’s one of the services I keep it on a pinned version and read release notes before updating.

Yeah, even when jumping minor versions they tend to spend a few days/weeks pushing patches, I’ll wait a bit before updating.

Glad you solved it yourself, but I’m still struggling to understand what happened, how did you have them all in a single folder if the filename for docker compose has to be one of a few predetermined things? I mean, you could have them all in a single file, which makes some things easier, but then you wouldn’t have been able to move them into individual folders. Would you mind explaining what happened there so that if someone else in the future has the same issue they might find the solution here?

Also, note that even if someone had given you an example of a working docker file you would still have to configure the service. For future reference, this site is great and has working examples of docker compose files for a lot of services, e.g. https://hub.docker.com/r/linuxserver/radarr

Finally, welcome to the club, sorry you had a bad experience the first time, it’s hard for us to know what’s obvious and what isn’t: https://xkcd.com/2501/

Plex server doesn’t need to be “portable”

Strongly disagree, I’ve switched my media server several times in the past decade for a multitude of reasons, having things in docker has allowed me to do this seamlessly.

Also you’re ignoring all of the other benefits of running in docker, from isolation to automation.

and running it in docker definitely doesn’t make it easier.

Plex is the only self-hosted service that is purposefully trying to block you from being ran in docker. All other things are just much easier to run in docker, that’s part of the appeal, reproducible builds eliminate the “it works on my machine” errors.

There absolutely are programs that make sense to run in docker, but Plex server isn’t one of them.

Why do you think it doesn’t make sense? Does Jellyfin make sense to you to run in docker? Why are they different?

Also, Plex only supports Ubuntu and CentOS, none of which I run on my server, so the only OFFICIAL way to run Plex is Docker.

There’s zero need to run anything in docker, it just makes things easier and portable.

What Plex does is closer to having an embedded tailscale client, you can access Jellyfin remotely with tailscale for free, but OP specifically asked for no VPN.

That being said, I’m not opposed to Plex charging for that service, even a tailscale like server costs something to maintain. My gripe with Plex is that it purposefully shoots itself in the foot to force you into their paid service, i.e. it actively tries to isolate itself so you can’t access it remotely, which means that it can’t run inside a docker container unless you give it network host access, otherwise it only considers other docker containers locals and doesn’t let you watch your own content from another machine in the same network.

Because clients would probably fail if there’s an authentication layer on front that they’re not expecting.

https://github.com/jellyfin/jellyfin/issues/5415 nothing too serious, but here you go

IIRC Envy clients can connect to Jellyfin, it’s part of the reason why they don’t change the API despite security issues.

Except most people have almost the same structure because of media organizers like radarr/sonarr. At the very least they should hide that behind a setting to not require auth (since the header should be there for most clients) so only people running an old client would be affected. They could also add an extra salt to that hash or something similar.

I agree, it’s not critical, but it shouldn’t be hand waved either. And like I said, security is relative, I would argue for most people this is fine, but I still think this should be taken more seriously.

Secure is relative, you should be aware that jellyfin itself has security issues https://github.com/jellyfin/jellyfin/issues/5415 most of which are harmless, but at least one is fairly serious and allows people to watch your media without authentication, and adding an extra layer of authentication on the proxy would likely cause issues with clients.

That being said, if you’re okay with those security issues what I would do is have a cheap VPS, connect both machines to tailscale, and have something like Caddy on the VPS to do the forwarding.