Set up a public throw-away demo #66

Closed
opened 2026-05-23 20:55:29 +00:00 by coilysiren · 1 comment
Owner

Originally filed by @coilysiren on 2026-05-02T23:06:34Z - https://github.com/coilysiren/repo-recall/issues/43

Stand up a public throw-away demo of repo-recall so people can poke at it without cloning and configuring locally.

Goals

  • Linkable URL that shows the dashboard against a representative dataset.
  • Disposable: assume it gets reset / torn down on a schedule, no durable user data.
  • Cheap to run and easy to redeploy from main.

Open questions

  • Hosting target (existing k3s homelab vs. a managed PaaS).
  • Demo dataset: synthetic seed vs. a snapshot of a public repo's recall data.
  • Auth posture: fully open, or a shared read-only token.
  • Reset cadence (nightly wipe? redeploy on push to main?).

Out of scope

  • Multi-tenant signup flow.
  • Persisting visitor-generated data across resets.
_Originally filed by @coilysiren on 2026-05-02T23:06:34Z - [https://github.com/coilysiren/repo-recall/issues/43](https://github.com/coilysiren/repo-recall/issues/43)_ Stand up a public throw-away demo of repo-recall so people can poke at it without cloning and configuring locally. ## Goals - Linkable URL that shows the dashboard against a representative dataset. - Disposable: assume it gets reset / torn down on a schedule, no durable user data. - Cheap to run and easy to redeploy from `main`. ## Open questions - Hosting target (existing k3s homelab vs. a managed PaaS). - Demo dataset: synthetic seed vs. a snapshot of a public repo's recall data. - Auth posture: fully open, or a shared read-only token. - Reset cadence (nightly wipe? redeploy on push to `main`?). ## Out of scope - Multi-tenant signup flow. - Persisting visitor-generated data across resets.
Author
Owner

Iceboxed in the 2026-05-29 backlog burn-down: Public throw-away demo, speculative external-facing play. Reopen anytime if it becomes real.

Iceboxed in the 2026-05-29 backlog burn-down: Public throw-away demo, speculative external-facing play. Reopen anytime if it becomes real.
coilysiren 2026-05-30 05:43:54 +00:00
  • closed this issue
  • added the
    P4
    label
Commenting is not possible because the repository is archived.
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/repo-recall#66
No description provided.