/public/* routes — always ungated, share button always points here
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 1
- Avg merge
- 7h 13m
- Merged PRs (30d)
- 31
Description
Share links must always work — no auth, no JWT, guaranteed reachable.
Add a /public/* route prefix that bypasses all auth. The share button should always generate a link to /public/apps/name, never to an authed endpoint.
Why this matters: A demo link that requires login from the audience kills the moment. This is critical path for the April 9 demo.
Acceptance criteria:
/public/apps/:nameroutes are ungated- Share button generates
/public/URLs - These routes survive tunnel restarts
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
Start by locating the route definitions and the share-button implementation. Trace how authentication is applied to app routes and how share URLs are generated, then verify the public paths remain reachable after tunnel restarts. Done means /public/apps/:name is ungated and the button consistently emits /public/ URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, backend, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100