Interesting, background sync was completely broken on the new beta timeline for me. I had to open the app, and disable then reenable sync every time I had new photos.

I’m back on the old version because it’s basically 100% reliable.

I’ve never had any issues with the old setup oddly enough, they talk like it barely functions lol

The app let’s you see/search all your photos, I have a ton of photos not on my phone.

Correct yeah, you’d still need a way on the host to check if the mount is ready though before starting the service. Or you could just do a fixed delay time.

For subdirectories it’s more complex as each application needs to be configured properly too, so you’ll need to go into transmission and tell it what subdirectory you’re using.

Or switch to subdomains as that just works without any extra config, and still let’s you use one port for everything.

You should be able to modify the docker service to wait until a mount is ready before starting. That would be the standard way to deal with that kind of thing.

There is barely any overhead with a Linux VM, a Debian minimal install only uses about 30MB of RAM! As an end user i find performance to be very similar with either setup.

That means it’s unlocked, but not factory unlocked.

But also can find listings that are factory unlocked if you’re worried about that.

I run debian on everything, so I set up unattended-upgrades for security updates and basically forget about it. Docker updates are also automatic with Komodo, just make sure databases are pinned to a major version.

For monitoring my services I use Uptime Kuma, and get an alert if a service goes down so I can fix it.

Been pretty solid for years now. Things get rebooted every month or two when I do a Proxmox upgrade and reboot the host.

It’s still great either way, there’s a lot of work into making it easier to use and less hassle.

Starting at only $58,995 I’m sure.

Display Port ftw

It really is, most people could probably be using Display Port anyways, unless trying to hook up to a TV I suppose.

Not the newer version of it, they’re stuck on the older one.

In the case of these ones you just remove the LXC/VM it created.

Install Debian as a server with no GUI, install docker on it and start playing around.

You can use Komodo or Portainer if you want a webUI to manage containers easily.

If you put any important data on it, set up backups first, follow the 3-2-1 rule by having at least 2 backups in place.

The problem with stuff like yunohost is when it breaks you have no idea how to fix it, because it hides everything in the background.

For local access you can use 127.0.0.1:80:80 and it won’t put a hole in your firewall.

Or if your database is access by another docker container, just put them on the same docker network and access via container name, and you don’t need any port mapping at all.

This only happens if you essentially tell docker “I want this app to listen on 0.0.0.0:80”

If you don’t do that, then it doesn’t punch a hole through UFW either.

How though? A database in Docker generally doesn’t need any exposed ports, which means no ports open in UFW either.

Linux lets you do whatever you want and that’s a side effect of it, there’s nothing preventing an app from messing with things it shouldn’t.