

Oops, you’re right! I had something there and deleted it before posting :)
Added a short sentence now, thanks for the heads up!


Oops, you’re right! I had something there and deleted it before posting :)
Added a short sentence now, thanks for the heads up!
You don’t need a “platform” if you just want a simple blog. I don’t know your values, but you can check mine: https://lnar.dev/blog/blog-setup/
I’m just getting my feet wet really, but I love that setup. The only change since that post is that I use Obsidian for editing (and some minor extension changes). It’s a shame Obsidian is not FOSS, but it also doesn’t matter as there is no lock-in and easy to switch.


Thanks! Hmm, not sure what you mean, that I shouldn’t install devDependencies when building the release? That’s a good point, I’ll need to look into it


Oh interesting! Thanks for explaining :)


Thanks for the explanation, makes sense! This app relies quite heavily on in-memory caches, so it’s somewhat incompatible with that model :)
That said, I wonder if the startup time would be noticeable. Depends a lot on the configuration, but it shouldn’t take more than a few 100ms (esp. if you use skip_collection_counts).


Thx! Out of interest, what is your use case?


I don’t know a lot about fastcgi, but looking it up it seems like it also keeps a persistent process running to avoid execution overhead, but I don’t know how that process is managed 🤷♂️
Either way, you could use a supervisor of sorts that shuts down the process/container after some idle time (at least for containers I know some exist) and that should probably work fine (outside of interrupting scanning operations).
I haven’t tried it myself yet though :)


Thanks for trying it out! Let me know if you run into any issues or have some ideas :)


Hey thanks! The Immich folks are doing an astounding job indeed :)


Let me know if you encounter any issues! ☺️


Hmm, I’m not sure I understand exactly. By default it uses each subfolder as an album / collection that you can pick on the home page. You can also configure custom collections/albums consisting of arbitrary directories. You could also configure e.g. an “all” collection with all the photos combined by listing the root directory(s). Is that what you meant?


Thanks! Do you mean explorer-like folder browsing?


Thanks!
You can run it on a subdomain, e.g. photos.mydomain.com with no special configuration, but it doesn’t support subpaths, e.g. mydomain.com/gallery/


No concrete plans for auth yet, but there’s an feature request for this. I didn’t really want to give a sense of false security with a half-baked solution.
For uploading, I thought about it briefly and it could be interesting. How would you expect it to work?
I imagine you would configure a sort of a target folder structure, then it would dump all uploads based in that structure? Or fully managed like GPhotos/Immich where the app hashes, dedupes and owns the files directly? 🤔


Ah, I see! This is more of a solution for viewing existing photos, it’s not a fully fledged multi-user photo management solution.
If you had family members access and share photos via a file share though, you could use this to set up a common gallery that everyone could access via the browser.
It’s mostly meant to run on a local NAS though.


Good to know, thanks for the info!


Depends on what you mean by sharing, but if you put all your photos on a local NAS and run this on it for example, then everyone with access to it would be able to see them through a browser.
There’s no explicit sharing feature though.


Thanks!
Unfortunately I have no idea about the Unraid ecosystem, so I’m not sure what’s the best way to approach that. It seems like you can run Docker images, so that’s probably one way to go? Let me know if you get it to work!
There’s an easy solution to that problem: grab a camera and get crackin’! 😁