I need to put some order with the photos I take and I receive with my android phone. Just now I use Nextcloud sync client to upload and Photo/Memories Nextcloud Apps to manage photos.
However, I am not very happy with this setup because of the lack of one Android Application for photos and, thus, the photo gallery of my phone is totally different to the Photo/Memories timeline. And photos are not deleted from my mobile phone when I delete them in Photo/Memories. Which selfhosted photo manager do you think is better to backup and manage photos in sync with the phone?
A second question, is it better to manage the photo gallery with a folder structure or with the album functionality of the Photo application? Which is the best interoperable solution? If I use albums in Memories then I can export those albums to Immich, Librephotos… ? Or I would have to create all the albums again after the export?
i’m a fan of immich, but i don’t think it deletes photos from your phone when deleting it on the server.
I wanted to try Immich but I quickly found out you can’t simply point it at an existing folder structure like say Plex or Jellyfin. You have to “import” all your files via a client and if you’re like me and already have thousands of images in Nextcloud then even with their bulk upload CLI tool it is too much of a hassle.
Plus I don’t want to be locked into their format, I want to be able to switch if the project goes under or I find something better later on. Nextcloud’s photo management is not great but I am willing to sack some speed and usability for using raw folders rather than a database.
Immich actually organizes your photos in a simple directory structure, which is customizable (want to group by year? year+month? by day? not at all?). The images are right there in your file system and have the original file name.
The directory is “read-only” though, for the same reason as there is a need to import existing libraries: database synchronization.
Immich offers many features that require a database or pre-processing of files, which makes it fast and feature-rich. If you modify files outside of Immich, it cannot know what changed and loses track of where your media is.As I said, the (read-only) file structure is always there in case you want to switch.
There’s an active pull request to add this in. Stay tuned
I didn’t see any unique format for how Immich stores photos, they’re just on the filesystem as images.
From what I understand (I could be wrong) all of the images get imported into a single folder and albums are done via the database. I currently have my albums in individual folders. So not only would I have to recreate dozens of albums but I don’t think there would be any way to export them in the future. But if that isn’t how it works maybe I will give it another go.
Storage Templates. Photos are stored in subdirectories categorized by date.
CLI Import. It looks like you may be able to import your albums with the cli and --album flag, not sure about exporting though.
Interesting. Being able to import them using the folders as albums is fantastic, although it seems like there is no {{album}} variable for the storage template so the problem still persists. Once I’m using it there would be no easy to way to export the albums out.
I tried photoprism and thought it was pretty neat feature-wise. If I recall correctly they even sort received photos in a sensible date-based structure automatically. Don’t think they have an official app but maybe some third party stuff; the web UI is mobile friendly though.
To talk backups, I’d deploy the thing using containers and then back up the volumes any way you like.
This may not be the ideal solution for you, especially due to lack of decent android support. The workflow would probably be something like take photo -> sync to protoprism to sort -> view in photoprism gallery, which may also be too convoluted for you. Also, I’m not sure what you mean by the last paragraph.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:
Fewer Letters More Letters CSAM Child Sexual Abuse Material NAS Network-Attached Storage Plex Brand of media server package
3 acronyms in this thread; the most compressed thread commented on today has 16 acronyms.
[Thread #134 for this sub, first seen 12th Sep 2023, 08:55] [FAQ] [Full list] [Contact] [Source code]
Round Sync with whatever remote (backend provider) you want supported by the underlying library rclone. They have self hosted remote options like FTP or something. If you want off site and privacy, create a crypted remote pointed to your off site backend remote. It acts as a wrapper to do end-to-end encryption.
Round Sync isn’t in any app store, so I’d set a watcher for releases on Github. You can setup scheduled backups or restores in Round Sync to keep things moving between your phone and backend remote as a relatively set it and forget it for one way syncing.
It has some nuances with bidirectional syncing that can result in data loss if not careful. With your workflow, I recommend something like a daily copy job from your phone to the server. This never deletes files. When you curate your photos via a tool on the backend remote (only do this when all photos on your phone are on the backup server), then you can do a manual sync from the backend remote to your phone to match the two exactly.
Copy just copies or updates to newer versions from target 1 to target 2.
Sync does the same but also deletes any files on target 2 that are not on target 1. Very easy to delete files if not careful in planning out your workflow. Test first.
I use Backblaze B2 for my off site remote which only hides and doesn’t delete files with the default settings. You can manage those with the rclone CLI application on a desktop to later cleanup hidden files or set them to delete after X days or something in the b2 life cycle settings on the Backblaze website.
Its no Google Photos or Dropbox, but it works well enough for me without giving up privacy. It also decouples the syncing from curating of photos giving some additional freedom for a custom workflow.
I personally just have a daily copy job on my phone from my phone to a crypted b2 remote and a cron on my self hosted server to copy from b2 to my self hosted server. Once a year I might clean things up from my server, do a manual sync to b2, then another to my phone. Sometime later I’ll go clean up the hidden (deleted) files in b2.
That said, I care more about backups than bidirectional syncing, so your milage may vary with this solution for your use case.
This repo may help: https://github.com/meichthys/foss_photo_libraries
This is a great question. The photo ecosystem is one where I haven’t found a FOSS soln that hits all the marks of subscription services. I would focus on whatever helps you search.
I do feel like if files have accurate dates in the file system and in metadata, then folders based on event make sense.
However subscription photo services are very good at automatically sorting - these dates are holidays so these pictures are probably for that holiday. Your home location is here, these pictures are over there so this must be your trip to there. These pictures have these people or animals, so these pictures are about them.
With that comes seamless integration across devices - a picture taken at time now can be seen on a tv or laptop at time +x. Etc.
I have left the FOSS photo world but am definitely interested to see where it is. With digital photography finding pictures is the real trick. using folders like a tag hierarchy at least gets you in the ball park imo. But I have no practical knowledge any more.
