That's an option, but I want to keep things simple and the assumption is usually "filesystem" but weirdly most libraries assume S3 usage.
I don't think I've seen native support for db-stored images in any of the libraries I use, which is sad but a reality.
Maybe not directly in libraries but there's a few programs to make a fuse filesystem backed by a database.
Ya cant just throw em at a blob type field/column?
In the git repo even
The images are supplied by the users, so that wouldn't be an option