Closed tborychowski closed 3 years ago
Thanks for the report. As discussed:
I thought I was the only one! I replied to the author on Reddit (if that's not you) that I was looking for exactly this, just a simple scanner/thumbnail/gallery view of large photo folders (50K+ images). I've tried about 7 app suggestions on Proxmox->Debian->Docker on a Dell R710 with a CIFS share mounted from a Synology array. Damselfly didn't work for me either, even after I installed twice from scratch and let it soak for over 24 hours. Never got thumbnails, justlots of errors in the logs about the generator crashing, etc. I didn't think of looking for a GitHub repo to raise an issue in (I'm not a developer or work in IT). I look forward to a new release!
Oh, weird. Can you attach a complete log file? Thanks. (author on reddit is me)
Yep, the same here. After 11 hours of running I still see no thumbnails.
I'm using a similar setup to @dupuik: CIFS folder from synology mounted on a ubuntu server. Have tried a lot of galleries and none had any problems with this (currently using pigallery).
Are the thumbs saved to the same folder? (as I have my synology folder mounted in docker as read only)
Here's my full log (folder names redacted for privacy 😉):
Did it create the thumbnail folder (.thumbnails in the root folder)? Wondering if it's a write perms issue.
Ah, just seen your comment about the folder being mounted as RO. That'll do it. Currently the thumbs are written to a .thumbnails folder in the root folder of where the pictures are. But I've never been happy about that as some people prefer the pics folder to be RO until they trust the software. So one of my todos is to change it so the thumbs are put in the /config folder, which makes more sense. Downside is for people running it, they'll need to move the thumbs.
But anyway, I'll try and make that change to the Docker build and push an update later today or tomorrow.
Also, the logs should indicate if the thumbs can't be written, but it looks like that isn't happening. Will fix.
Damselfly can modify your originals - to add/change/remove IPTC tags on your images (assuming you use that function in Damselfly). However, it's all done via Exiftool so will only modify the exif data.
I'm doing a new version which will put the thumbs in the config folder, which makes much more sense and means you can leave the photos RO. Should be ready later today or tomorrow.
@Webreaper wouldn't it make more sense (for docker users) to use a separate mount for the thumbs folder? e.g.:
Yeah, I was going to provide a second mount for the thumbnails, which will default to /config/thumbs if you don't explicitly override it.
Looking at it now. Funny that we both worked at the same place!
Okay, so I've put in some fixes to make this work a bit more reliably, and to do on-demand thumbnail generation (rather than it all being in batch). I've also updated docker so you can specify a volume for thumbs. I've pushed it to the dev channel, so you can try something like this:
docker run \
--name damselfly \
--restart unless-stopped \
-v /volume1/dockerdata/damselfly:/config \
-v /volume1/dockerdata/damselfly/thumbs:/thumbs \
-v /volume1/photo:/pictures \
-p 6362:6363 \
-d \
webreaper/damselfly:dev
Let me know if it works a bit better!
Outstanding! Trying it now as a fresh install. To see how fast it goes and if I get thumbnails to display on the main page.
@.***:/docker/damselfly# grep "model name" /proc/cpuinfo model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz model name : Intel(R) Xeon(R) CPU X5650 @ 2.67GHz
@.***:/docker/damselfly# df -h|grep photoalbum //vangogh/photoalbum 913G 395G 519G 44% /vangogh/photoalbum
@.***:/docker/damselfly# w 22:39:08 up 10 days, 2:33, 1 user, load average: 0.49, 0.27, 0.19
@.***:/docker/damselfly# cat docker-compose.yml services: damselfly: image: webreaper/damselfly:dev container_name: damselfly restart: unless-stopped volumes:
On Sun, Mar 28, 2021, 10:16 PM Mark Otway @.***> wrote:
Okay, so I've put in some fixes to make this work a bit more reliably, and to do on-demand thumbnail generation (rather than it all being in batch). I've also updated docker so you can specify a volume for thumbs. I've pushed it to the dev channel, so you can try something like this:
docker run \ --name damselfly \ --restart unless-stopped \ -v /volume1/dockerdata/damselfly:/config \ -v /volume1/dockerdata/damselfly/thumbs:/thumbs \ -v /volume1/photo:/pictures \ -p 6362:6363 \ -d \ webreaper/damselfly:dev
Let me know if it works a bit better!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Webreaper/Damselfly/issues/119#issuecomment-809019628, or unsubscribe https://github.com/notifications/unsubscribe-auth/APBUYSP676IJE4CO64JISC3TF7WKLANCNFSM4Z5IHT5Q .
Should I see some thumbs now? It's been running for 4 hours. I added it to my home start page as an official app now ;)
@Webreaper dev
tag works for me, thumbnails are generating almost instantly!
thanks!
Great to hear, @tborychowski .
@dupuik Yry shift-refreshing the page, and you should see thumbs.
@dupuik Yry shift-refreshing the page, and you should see thumbs.
Finally! After ~8 installs, using the dev image now, tweaking the environmental variables (SYNO_THUMBS was preventing any thumbs from showing up) and mounting the Synology share read-write on the Proxmox->Debian->Docker host, I'm getting thumbs when I clear cache and load the main page after the latest install from scratch!!! I'm seeing ALL my photos in one place for the first time since Google Picasa shut down years ago!!!
Closing it now, as it's fixed. Thanks for a quick response and the fix!
FYI, this has now been released (https://github.com/Webreaper/Damselfly/releases/tag/1.6.6-beta) so you can switch back to :latest from :dev tag with your docker configs.
I'll try it again. I noticed weird behavior with thumbs even after 2nd fresh install 2 weeks ago.
On Thu, Apr 8, 2021, 6:35 PM Mark Otway @.***> wrote:
FYI, this has now been released ( https://github.com/Webreaper/Damselfly/releases/tag/1.6.6-beta) so you can switch back to :latest from :dev tag with your docker configs.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Webreaper/Damselfly/issues/119#issuecomment-816275934, or unsubscribe https://github.com/notifications/unsubscribe-auth/APBUYSJ4A2L7D56KLMAHWGDTHYVS5ANCNFSM4Z5IHT5Q .
I used the docker-compose example from the readme and started the container (providing a folder from my Synology with pictures). It has loaded the images and parsed the tags (as I can see the folders and other metadata displaying in the UI). However the photo thumbnails do not show up:
and the log shows this:
[click to expand]
``` damselfly | [20:14:27.787-0082-WRN] Unhandled exception rendering component: A task was canceled. damselfly | System.Threading.Tasks.TaskCanceledException: A task was canceled. damselfly | at Microsoft.JSInterop.JSRuntime.InvokeAsync[TValue](Int64 targetInstanceId, String identifier, Object[] args) damselfly | at Microsoft.JSInterop.JSRuntimeExtensions.InvokeVoidAsync(IJSRuntime jsRuntime, String identifier, Object[] args) damselfly | at Microsoft.AspNetCore.Components.Web.Virtualization.VirtualizeJsInterop.DisposeAsync() damselfly | at Microsoft.AspNetCore.Components.Web.Virtualization.Virtualize`1.DisposeAsync() damselfly | at Microsoft.AspNetCore.Components.RenderTree.Renderer.