Hey, that looks awesome. I'll try it out when I get back from work.

Edit: This is awesome! It satisfies my requirements and goes beyond. Great app!

That's a pretty good idea, actually. I'll try that out. Thanks.

Thanks, I took a look. It's very close to what I want, but it still doesn't support uploads in shared directories. It seems to be a pretty highly requested feature though. So maybe it'll happen at some point.

Storage, RAM, CPU usage. I prefer not to have such a large piece of software running for no reason. It might seem silly, but I hate using resources for no reason. I'll rather have 5 lightweight apps running instead of a huge one, of which I'll only use a few parts.

I'm strictly against Nextcloud or something similar. I prefer to run a bunch of lightweight apps, rather than one big one.

I don't care too much about security, since I'll delete everything in a few days after copying them to my gallery. Then, I usually share a link with them to an album on my PhotoPrism instance. So, per share password is fine by me.

Yeah, but that's already possible with my current setup using FileShelter. I'd like them to be able to upload as well.

This looks pretty promising. Do you know if it's possible to add per-share passwords, so that I don't need everyone to open an account?

Edit: It's not.

Yeah, it's a bit too much I think.

Thanks for the insight. They submitted said they're willing to help with future issues, so I guess I don't need to worry about it too much. (I can just discontinue k8s support if they don't keep their word.)

Upon further testing, this does actually work. You may set both read_only: true, and cap_drop: all and it will work as long as you have a named volume. I had it mount a database file from the host system for my test config, which is why I was getting the errors. I don't know how to make that work though i.e. when the db is bind mounted from the host system. Setting the mount :rw doesn't seem to fix it.

That's great to know. Btw, you don't actually need to specify the url path for it to work. That's just for convenience of copying the link from the UI. It'll just work as long as the server is reachable at that address.

Thanks. I had never tested this before. Seems like it throws errors. Of course, adding and deleting links don't work. But that's to be expected. But also link resolution fails since it cannot update the hit count properly. If this is a legitimate use case for you, I might work on making it work.

Like the other guy said, it's not necessary. But docker makes it much easier to deploy. There are instructions to set it up without docker as well.