Skip to content

Local object store (development) reference #564

Closed

Description

@codebestia

Write apps/backend/docs/concepts-local-object-store.md for lib/localObjectStore.ts and the localStorage route: the filesystem-backed implementation of ObjectStoreLike used in development and test so presigned upload/download URLs actually work without MinIO.

Acceptance criteria:

  • Documents the ObjectStoreLike surface both implementations satisfy, including headObject used by upload-confirm verification
  • Explains where bytes land on disk, the signed local URL format, and how the serving route validates expiry and signature
  • Documents the production/development selection and confirms no call-site changes between them
  • States that this keeps the test suite free of Docker, consistent with the project's no-external-services rule

Activity

  1. Marywase commented on Sep 28, 2026

    @Marywase

    @Marywase has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Hello maintainer, if assigned, I’ll trace localObjectStore.ts and the localStorage serving route, document the shared ObjectStoreLike surface including headObject, explain the on-disk layout and signed URL validation, and clearly cover how development and production implementations are selected without changing call sites. I’ll also make sure the no-Docker test requirement and local upload and download flow are accurately reflected.
    Thank you!

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Marywase to this issue.

  2. Damola09 commented on Sep 28, 2026

    @Damola09
    Contributor

    @Damola09 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

    Can i work on this?

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @Damola09 to this issue.

  3. drips-wave commented on Sep 28, 2026

    @drips-wave

    Congratulations, @Damola09! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

    🧑‍💻 @Damola09: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  4. added a commit that references this issue on Sep 29, 2026
    f81fd2a
  5. github-actions commented on Sep 29, 2026

    @github-actions

    Closed by #611, merged into dev.

  6. drips-wave commented on Sep 29, 2026

    @drips-wave

    This issue has been completed by @Damola09 as part of the Stellar Wave Program's 9th Wave 🥳

    😎 @Damola09: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

    🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programbackenddocumentationImprovements or additions to documentationinfra

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions