aiolabs/restaurant
8
0
Fork 0
Code Issues 11 Pull requests Projects Releases Packages Wiki Activity Actions

docs: rename castle → libra in design-conversation example

Browse source 
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) <noreply@anthropic.com>
This commit is contained in:
Padreug 2026-05-05 20:44:58 +02:00
commit e2a2f4a633
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/design-conversation.md
View file

@ -273,7 +273,7 @@ is it feasible to turn this into an lnbits extension? ref to folder ~/dev/shared
## Assistant ## 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 ## User