yeah, it’s only job is to serve photos yet it needs a whole linux container to run… i get why some people like it but i said it’s not what i want.
Comment on please recommend a simple selfhosted photo gallery
non_burglar@lemmy.world 3 weeks agoIt does nothing but serve photo. Background tasks are minimal and many of them only run once on new photos.
hexagonwin@lemmy.today 3 weeks ago
non_burglar@lemmy.world 3 weeks ago
I mean, you say contradictory things in your post: you don’t want to manage a db, but you want to assign tags and categorize the photos, which would need a db of some kind.
If you really, really don’t want a db but you want web access to your pics, just rename them so they sort alphabetically the way you want and drop them in the doc root of a www server, apache or nginx would work. Do note that you will have no sorting or tagging options, but it will be dead simple. This is what the copyparty option would give you.
Not sure what you mean about “a whole Linux container”, the majority of my alpine images run in under 100MB memory and use less than 0.1% CPU, so it’s not clear to me what your objection is.
@non_burglar @hexagonwin @WeirdGoesPro
I prefer #copyparty as an allrounder for serving static files (images and videos from my smartphone) - https://github.com/9001/copyparty
Uploading from my smartphone via #nextcloud on iOS into a shared folder for NC and CP 🤓
non_burglar@lemmy.world 3 weeks ago
OK? By all means, use what works for you.
I personally wouldn’t go around using copy party’s initials liberally like that.