Early access · we're not open yet
Your project's Discord answers help one person, then disappear. The same questions get asked again next month. We're building a chat where Q&A channels render to the open web by default. Indexed by Google, owned by you.
Most OSS projects ended up using Discord for support. That made sense in 2019. It stopped making sense around the time you noticed you'd answered the same question for the fifth time.
The answer you wrote was good. It scrolled off the channel in three days. Nobody else who hits the same problem can find it. Some of them ask again. Some of them stop using your project. More answers don't fix this; they make it worse.
A community chat with two kinds of channels.
Any pod mixes them however you want. Promote a single thread from a private channel into the archive (with consent from anyone quoted). Pull a thread back to private without deleting it. Members get one consent prompt before their first public post, and a one-click delete later.
Hosting from us, or self-host. The archive's yours either way.
brine
typescript orm · community archive
I'm trying to use Brine with Cloudflare D1 as the backing database. The docs cover Postgres and SQLite but I can't find which adapter to pass for D1. Has anyone got a minimal working setup? Bonus points if you've also got migrations running via wrangler.
D1 uses the SQLite wire protocol, so the right adapter is @brine/sqlite with the D1 driver shim. Minimal config:
// brine.config.ts
import { defineConfig } from '@brine/core';
import { d1Adapter } from '@brine/sqlite/d1';
export default defineConfig({
adapter: d1Adapter(env.DB),
schema: './schema.ts',
migrations: { directory: './migrations' },
});For migrations under Wrangler, point wrangler.toml at the same directory and run brine migrate --remote before deploying.
One more thing: if you're on Brine 0.4 the d1 shim is built into @brine/core directly, no separate package needed. Was a 2.0 plan that landed early.
↑ A Q&A page from a hypothetical archive. Mockup, not yet built.
✓ Yes
✗ Not yet
We're trying to find out if this is worth building before we build it. If you'd use it, tell us. If you wouldn't, tell us that too. Either answer saves us six months.