For troubleshooting, I would recommend you visit the Plex Discord/Matrix channels for real-time help. Additionally, !plex@lemmy.ca may prove helpful.
I’ll leave this for others to chime in. But you may find useful information in one of the homelab communities as well.
OP says the question has been answered. Locking the discussion so they don’t have to suffer through any more repeat information.
Not from iCloud, just from the phone’s local storage. So, to backup all of iCloud from the phone, those photos would have to be downloaded to the phone first.
Alternatively, you can download all the photos from iCloud to a computer, then upload those photos manually to the Immich web interface.
I have implemented what you’re looking for using Immich on my wife’s iPhone.
Immich backs up the “Recents” album - which means it backs up everything. What’s important to remember is that it backs it up, not syncs it. This allows me to delete photos from the iPhone and they stay in the Immich library. This is how I keep my wife’s phone from running out of storage.
Works well for us so far, even if I have to manually delete the photos off the phone from time to time.
In fairness, the lack of Enterprise OS connectivity is spelled out in the Pricing breakdown on their website.
While this post is in support of a self-hosting platform, the request itself is storage-related. I would recommend that you reach out to https://lemmy.world/c/zfs or https://discourse.practicalzfs.com.
This sounds like something you should pursue on the project’s GitHub page: https://github.com/immich-app/immich
The problem with managing replication outside of PVE is ‘what do you do when you have to move the VM/CT to another node?’ Are you going to move the conf file manually? It’s too much manual work.
Let PVE manage all of the replication. Use Sanoid for stuff that isn’t managed by Proxmox.
Home assistant integration could accomplish this for you. Not sure if it’s less work than regular mobile clients, though.
I think fans of Nix and NixOS would agree.
view more: next ›
TL;DR: Op needs to sort out reverse proxy with SSL/TLS.