public/geek-cookbook
1
0
Fork 0
mirror of https://github.com/funkypenguin/geek-cookbook/ synced 2025-12-29 17:41:44 +00:00
Code Issues Releases Wiki Activity

Fix markdownlint, add Discourse page

Browse Source 
Signed-off-by: David Young <davidy@funkypenguin.co.nz>
This commit is contained in:
David Young
2022-08-23 10:47:09 +12:00
parent 956ebe8c38
commit 45a851df7a
30 changed files with 132 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
docs/review/immich.md
View File

@@ -74,7 +74,6 @@ The Mobile app seems very polished, and based on my testing, works better than t
<figcaption>Apparently this was 4000+ photos!</figcaption>
</figure>
### Other
Here's what the filesystem where photos are stored looks like:
@@ -100,7 +99,7 @@ Here's what the filesystem where photos are stored looks like:
/var/data/immich/upload/cae22784-474c-4527-825c-46d7f324e8e8/thumb/WEB/2245d33b-fbc5-40ee-a50b-2a234f73e3d9.jpeg
```
As you'll note, while it's true that files are stored locally, there's no filesystem-level metadata easily parsable, like yearly or album-based folders. While the files are stored locally, and *technically* you could move them elsewhere, it certainly wouldn't be easy.
As you'll note, while it's true that files are stored locally, there's no filesystem-level metadata easily parsable, like yearly or album-based folders. While the files are stored locally, and *technically* you could move them elsewhere, it certainly wouldn't be easy.
It's also not easy to access the files via any sort of sharing (*NFS, SMB, etc*), other than using the Immich UI. Par for the course though, I expect, if we want to be able to rely on the database for metadata without requiring intensive filesystem interaction.