WebDAV server. That's all it does.
Go to file
Neale Pickett fe8a1954f6 Mention dufs 2023-04-02 21:12:58 -06:00
cmd/webfs Move to alpine edge for ffmpeg 6 2023-04-02 17:30:02 -06:00
web GET / => index.html 2023-03-04 13:27:15 -07:00
Dockerfile Move to alpine edge for ffmpeg 6 2023-04-02 17:30:02 -06:00
LICENSE.md License: now with unicode! 2023-03-04 13:39:08 -07:00
README.md Mention dufs 2023-04-02 21:12:58 -06:00
build.sh initial version with thumbnailing 2023-03-04 11:17:11 -07:00
docker-compose.yaml Re-add thumbnailing 2023-04-02 13:04:30 -06:00
go.mod Re-add thumbnailing 2023-04-02 13:04:30 -06:00
go.sum Re-add thumbnailing 2023-04-02 13:04:30 -06:00


Notice: Something Better Exists

After working on this for a few weeks, I found dufs, which I am now using instead of this.


It's a WebDAV server that generates and caches media thumbnails.

I front-end it with Caddy, which handles authentication and access controls. Because the thumbnails live at the same path as the original media, so I don't need any special gubbins to protect thumbnails the same way.


If you put ?thumbnail at the end of the URL, it will use ffmpeg to generate a WebP thumbnail that fits in a 320x200 box.

I use WebP because it provides alpha channels, animations, and good compression. If your browser doesn't have WebP support, that's a real pity, and this isn't a good software solution for you.

Thumbnails are cached. No attempt is made to verify whether thumbnails are up-to-date, or to clean up the thumbnail directory. Something else is going to have to manage that.