No description
padreug
a77145e08e
The previous implementation used db.execute() with a raw dict, which failed on SQLite because the 'extra' field (TicketExtra model) was passed as a Python dict that SQLite cannot serialize. Using db.insert() with the Pydantic model ensures proper JSON serialization of the extra field across all database backends (SQLite, PostgreSQL, CockroachDB). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .github/workflows | ||
| static | ||
| templates/events | ||
| tests | ||
| .gitignore | ||
| .prettierrc | ||
| __init__.py | ||
| API_DOCUMENTATION.md | ||
| config.json | ||
| crud.py | ||
| description.md | ||
| LICENSE | ||
| Makefile | ||
| manifest.json | ||
| migrations.py | ||
| models.py | ||
| package-lock.json | ||
| package.json | ||
| pyproject.toml | ||
| README.md | ||
| services.py | ||
| tasks.py | ||
| toc.md | ||
| uv.lock | ||
| views.py | ||
| views_api.py | ||
Events - LNbits extension
For more about LNBits extension check this tutorial
Sell tickets for events and use the built-in scanner for registering attendees
Events alows you to make tickets for an event. Each ticket is in the form of a unique QR code. After registering, and paying for ticket, the user gets a QR code to present at registration/entrance.
Events includes a shareable ticket scanner, which can be used to register attendees.
Usage
-
Create an event
-
Fill out the event information:
- event name
- wallet (normally there's only one)
- event information
- closing date for event registration
- begin and end date of the event
-
Share the event registration link
-
ticket example
-
QR code ticket, presented after invoice paid, to present at registration
-
-
Use the built-in ticket scanner to validate registered, and paid, attendees
