Commit

7e0f4a2

Looked around. There are 2 generations here: legacy src/ + lib/ (express/fastify, firebase auth, docker) and service/ (bun + elysia, data/ -> local server -> supabase -> static site). What's bugging you most: auth, sync flow, or supabase?
Haha I want to redesign the whole thing. About current infra, what I didn't like: ・ Dependent on VS Code, which I haven't opened in 4 months ・ Requires a laptop to write, I want a nice backoffice ・ That the vault lives in a gitignored dir in the repo, so it's like nesting repos…
Shape I'm picturing: a Bun CLI you run in the vault under pitchfork. It indexes the .md, serves a web backoffice, commits+pushes with a GitHub App token, and publishes to Supabase on save. Q: always-on box or laptop?
Then Dokploy could own it: one Bun container, vault = git clone in a volume, GitHub App token pulls/pushes, backoffice behind your existing Supabase login. Keep mise+pitchfork for local dev only, or run it bare on the host?

commit 7e0f4a2