this post was submitted on 30 Apr 2025
61 points (95.5% liked)

Selfhosted

46546 readers
2310 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I thought of this after a recent trip with some friends. We shared the photos when we were still in person. But sometimes we need to share a lot of photos over the internet. In the past, we have used a shared google drive directory for this. But I'd prefer a self-hosted option. There should be some sort of password protection as well (ideally per share, and no need for accounts). One should be able to both access the current files and upload new ones, just like google drive or dropbox.

I currently have FileShelter, which works for 1-to-1 sharing but not for groups. I guess something like ProjectSend would work, but it's too complex for my usecase. I'd prefer something more lightweight since I'll maybe use it once every few months. Also, it should be noob-friendly, and accessible using a browser.

Update: I'm very happy with copyparty. It does what I want, and much much more. I even replaced my older webdav server with it since it provides more granular control over share locations and permissions. Kudos to the developer @tripflag@lemmy.world!

you are viewing a single comment's thread
view the rest of the comments
[–] Darkassassin07@lemmy.ca 7 points 1 day ago* (last edited 1 day ago) (1 children)

You could setup a user account like the share you're describing. There's a setting to prevent the user from changing their password.

Just pass out those credentials to anyone you want to collaborate with; they don't need their own individual accounts.

[–] SinTan1729@programming.dev 2 points 1 day ago (1 children)

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

[–] q7mJI7tk1@lemmy.world 2 points 1 day ago (1 children)

Yes, as @Darkassassin07@lemmy.ca says, just create a new user for each event you want to share photos about: 'BeachBBQ', 'WeekendStay-July' etc, then bind those user accounts to whatever folders you want to have the photos in and set the user restrictions to upload, share, but not delete for example.

I also use various FileBrowser instances, with a different subdomain pointing to them, also as a way to filter out usage as well. collegefriends.mydomain.com could take you to a FileBrowser instance that only has access to photos from a certain friend group. Not sure how useful that would be to you, but it's another way of controlling the data flow.

[–] Ulrich 1 points 1 day ago

just create a new user for each event you want to share photos about: 'BeachBBQ', 'WeekendStay-July' etc

I use Immich for that. You just create a shared link and then tick the setting to allow other users to upload.

Won't work for other filetypes though.