🖧🗫🤝 Collaboration tools 🛠⚒🚧 (git, forges, bug trackers 🔎🪲, gitea, gitlab)

132 readers

1 users here now

This is going to generally be about git forges like gitea, but it’s open to discussion about any collaboration assisting tools and platforms.

Related communities: !librecomms@scribe.disroot.org

founded 5 years ago

MODERATORS

freedomPusher@sopuli.xyz

Any reason we can’t have secret public repos in gitea? The public/private choice misses some use-cases. (lemmy.sdf.org)

submitted 3 weeks ago* (last edited 3 weeks ago) by evenwicht@lemmy.sdf.org to c/collaboration@sopuli.xyz

5 comments fedilink hide all child comments

I need a repo that should not be publicly findable with explore. Does this mean the repo necessarily must be private? When it’s private, I cannot simply give an URL to friends to browse. IIUC, they must create an account, tell me their username, then I must add their username as a collaborator. That’s way overkill.

I just want to give out an URL that will reach the content when visited. It should not be discoverable by the general public but we are not talking state secrets. It must be hassle-free for read-only access. When browsing to a private repo (when logged out), it gives a 404 error.

update: A hack comes to mind: I could create a 2nd account on the same server, make that account a collaborator, then share the password to that acct with friends.

you are viewing a single comment's thread
view the rest of the comments

[–] p_consti@lemmy.world 4 points 3 weeks ago

While that is the main way how pages are discovered, some scrapers also just try random URLs, or known words from leaks