keybase.pub symlinks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
WOW guy you are really cool!
I don't think client repo is good place for this issue but I could not find better. The problem is keybase.pub server do not follow symlinks.
For example I have file at https://farwayer.keybase.pub/arch/mobile/mobile.db.tar.xz and symlink to this file at https://farwayer.keybase.pub/arch/mobile/mobile.db. Server returns 404 for symlink. Correct behavior is return the file or redirect to file location.
My use case: I want to share my ArchLinux repo for React Native and Android developers. And preferred way to provide repo info is with symlinks.
P.S. For now I copied files as workaround.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no client file, test, or entry point; start by locating the keybase.pub server responsible for serving symlinked paths and reproduce the two linked URLs. Done means a symlink serves the target file or redirects to its location, with coverage for the reported path behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100