Regarding authentication, someone who has an account (in this case just yourself) can create password-protected shares which other people can browse, or upload, or browse+upload to (configurable when creating the share).
There is WebDAV support, and it should integrate well enough with shares, but I haven’t tested that specifically.
It has photo and video thumbnails, and a basic image-viewer, and with some elbow-grease it can also show exif-tags (gps-coordinates etc).
There is also optional file dedup, so if two people upload the same file, it’ll detect and skip that during the 2nd upload (doesn’t waste any bandwidth) and swap out the new file with a symlink to the existing one. Default disabled to avoid surprising someone with symlinks.
I think the following command would be enough to get you started:
but since that’s entirely unreadable, you can do it with a config file instead,
[global]
e2dsa # enable filesystem indexing
e2ts # enable media indexing (music tags)
shr: /shr # enable shares under this url
[accounts]
sintan: yourpassword
[/] # create a volume at this url
/srv/share/partypics # the filesystem path to share
accs:
sintan: A # give sintan read-write-move-delete-admin
and use it like this:
python3 copyparty-sfx.py -c the.conf
there’s another example here and here for inspiration.
Mind if I suggest my own software, copyparty?
Regarding authentication, someone who has an account (in this case just yourself) can create password-protected shares which other people can browse, or upload, or browse+upload to (configurable when creating the share).
There is WebDAV support, and it should integrate well enough with shares, but I haven’t tested that specifically.
It has photo and video thumbnails, and a basic image-viewer, and with some elbow-grease it can also show exif-tags (gps-coordinates etc).
There is also optional file dedup, so if two people upload the same file, it’ll detect and skip that during the 2nd upload (doesn’t waste any bandwidth) and swap out the new file with a symlink to the existing one. Default disabled to avoid surprising someone with symlinks.
I think the following command would be enough to get you started:
but since that’s entirely unreadable, you can do it with a config file instead,
and use it like this:
there’s another example here and here for inspiration.