It basically creates a second pointer to the same inode which makes file moves instant. So instead of copying the data to a new location and deleting it from the old it points to the existing inode immediately. You can’t do it across filesystems though so that’s why trash guides recommends using /data/media/tv and /data/torrents instead of the /tv and /downloads paths the lsio setup suggests since docker treats top level folders as different file systems.

It’s mostly useful for torrents in my experience when you need to reseed stuff but also don’t want to point Jellyfin/Plex to a live downloads directory for security reasons.

You’ll probably get better help if you post your config and any logs. Caddy may not log an entry to a file but you can watch the console logs to see everything (podman logs caddy or similar.)

This just boils down to basic opsec. Be careful what you post/comment, continue to use a generic username, stuff like that.

I always appreciate people putting up quadlet content. I’ve switched over almost my entire lab to it aside from Nextcloud (so thanks!) and a couple containers that have weird network quirks