So your pictures are automatically backed up using the Immich mobile app? That’s probably good enough anyway. If you want to, you can always setup something like Syncthing to get other files as well.
I can imagine. I just skimmed through their Github page and saw the claim:
inverse unix philosophy – do all the things, and do an okay job
These swiss army knives of software can be challenging. But I guess that’s also true for Nextcloud, probably even more so.
To be honest, I don’t really have a use-case for it, because I don’t really need any of the sharing and collaboration features which are kind of the main point imo. The only compelling reason is that I read somewhere that it is a good option to backup mobile devices. I know that Nextcloud is a real beast of a software and there are probably some more lightweight options out there for that purpose.
I never heard about any of those two, but it looks like file browser is going to be archived in September if that is the one you mean.
Yeah, that keeping things separate approach seems to be a good idea. It is just that idea that I can interact with my data from within various different tools, has some kind of appeal to me.
I already use Docker and docker-compose for all the services I host. They are also all configured to use bind mounts instead of volume mounts, so that I am in control where everything is located. I mainly use the official documentation although I sometimes like to check https://github.com/Haxxnet/Compose-Examples/tree/main. I didn’t came across any major problems with that workflow so far, but that is also besides the point of my original question.
Jellyfin is a good example of the workflow I had in mind. I have a media share on my NAS and just point Jellyfin to that share in the docker-compose. But that is not how things like Paperless work, at least not from my (still limited) understanding of it. I think there are other workflows, but the main one of Paperless is a consume directory and a data/media directory. Everything in the consume directory gets ingested by Paperless and is moved with (I think) a different hierarchical structure and filename to the media directory. So if I point the consume directory to my current documents share on the NAS everything is moved away. I am sure there are ways to specify how Paperless organizes the media directory, but it most certainly will not be exactly the same as before. So making the data/media directory function as my new NAS “share” will also result in a change. In addition to that, my documents share on the NAS also contains data that I probably don’t need to track with Paperless e.g. some spreadsheets. I am not sure how Paperless handles documents in the media directory that were not originally processed using the consume folder or if that is even a good idea in the first place.
I didn’t know it has that feature, but that’s quite nice.
Yeah, i think it’s the same for Paperless and Immich. It is just a different approach. If you have tags, facial recognizion/OCR, some form of album/collections and other searchable metadata it doesn’t really matter how it’s organized in the filesystem because you can search it easily.
It’s this metadata that opens up the possibility of a separate frontend and backend. Whereas in the olden days it was backend all the way with meticulously naming files and folders.
It is probably better to let the tools handle it themselfs instead of forcing your old habits onto the tools.
Thanks for the whole writeup about your Immich experience. I am definitely coming back to it, when I test it out.