Community & ecosystem
Where do I ask questions or report bugs?
GitHub issue trackers, per repository — there is no forum, Discord, or discussions board today, and this page will say so until that changes:
| About | Where |
|---|---|
The core library, with*() services, on-/in-/as-/by-/at- satellites | noy-db/core issues |
The extended to-* stores (postgres, aws, cloudflare, supabase, …) | noy-db/to issues |
The UI family (@noy-db/ui, @noy-db/ui-nuxt) | noy-db/ui issues |
| This documentation | the noy-db tracker |
Security reports are the exception: never a public issue — use GitHub's private vulnerability reporting on the noy-db repository (see the threat model).
Questions are welcome as issues; recurring ones become FAQ entries.
Is there a marketplace?
No marketplace — and here is the more useful answer: the extension points are published contracts, so you don't need one. Every satellite family binds exactly one frozen subpath of @noy-db/hub, which means anyone can build and ship their own adapter without noy-db's cooperation:
- More store adapters — the
to-*catalog already spans 22 stores across two repos (3 essential innoy-db, 19 extended innoy-db-to: cloud object stores, SQL, serverless databases, remote filesystems). All bind the same published@noy-db/hub/tocontract. - Write your own store — implement
NoydbStore(and optionallyNoydbPodStore) from@noy-db/hub/toagainst a ranged@noy-db/hubpeer dependency. Thenoy-db-torepository is the working reference: nineteen adapters built exactly this way, each validated by the same conformance tests yours can run. Your package never sees plaintext — the contract hands you ciphertext envelopes, which is why a third-party store requires no trust review of its author. - Other plugin kinds — the same pattern per family: unlock methods bind
/on, export formats/as, framework bindings/in, sync transports/by, sealing providers/at. The Families & ports page defines each seam.
Data-shape templates?
The recipes double as today's shape gallery — each ships a complete typed schema you can copy: invoices and clients (accounting), notes (personal notebook), a per-user preferences envelope (user preferences), MIME email records (email archive). A standalone template gallery is planned but does not exist yet; until it does, start from the recipe closest to your shape.
See also
- FAQ overview — the other evaluator questions.
- Recipes — including the "compose your own" path when nothing matches.