From e2a2f4a633aae23143ac3b778e7d6fb03c4932b1 Mon Sep 17 00:00:00 2001 From: Padreug Date: Tue, 5 May 2026 20:44:58 +0200 Subject: [PATCH] =?UTF-8?q?docs:=20rename=20castle=20=E2=86=92=20libra=20i?= =?UTF-8?q?n=20design-conversation=20example?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The castle LNbits extension was renamed to libra. Updating the parallel-extension reference in the design-conversation notes. Co-Authored-By: Claude Opus 4.7 (1M context) --- docs/design-conversation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/design-conversation.md b/docs/design-conversation.md index 5acfea9..d111b75 100644 --- a/docs/design-conversation.md +++ b/docs/design-conversation.md @@ -273,7 +273,7 @@ is it feasible to turn this into an lnbits extension? ref to folder ~/dev/shared ## Assistant -Feasible, yes — but it's a real rewrite. The Fastify+Prisma+TypeScript backend would need to become Python/FastAPI with LNBits' DB layer (look at `nostrmarket` or `castle` for parallels — postgres is supported). The Vite SPA can be served from `static/` or embedded in Jinja templates. Main win: LNBits replaces BTCPay for payment flow and gives you wallets/auth for free. Main cost: porting routes and Prisma schema to LNBits-style migrations. Want a rough mapping plan? +Feasible, yes — but it's a real rewrite. The Fastify+Prisma+TypeScript backend would need to become Python/FastAPI with LNBits' DB layer (look at `nostrmarket` or `libra` for parallels — postgres is supported). The Vite SPA can be served from `static/` or embedded in Jinja templates. Main win: LNBits replaces BTCPay for payment flow and gives you wallets/auth for free. Main cost: porting routes and Prisma schema to LNBits-style migrations. Want a rough mapping plan? ## User