c84b4c5f97
Jetstream was running backgrounded in the same container as the API server, so crashes went undetected and Docker never restarted it. Now each process runs as a separate docker-compose service with independent restart policies. Also adds cursor persistence to SQLite (saved every 5s) so restarts resume from where they left off, moves event destructuring inside try/catch blocks, and adds global unhandled error/rejection handlers for crash visibility.
litenote-jetstream
Backend for Remanso, a blogging platform on the AT
Protocol. Listens to the Jetstream firehose for space.remanso.note records and
serves them via a REST API.
Prerequisites
Setup
# Initialize the SQLite database
deno task migrate
Development
# Run the Jetstream listener (with watch)
deno task jetstream
# Run the API server (with watch)
deno task server
Production
# Run both processes
deno task jetstream:prod & deno task server:prod
Docker
docker build -t litenote-jetstream .
docker run -p 8080:8080 -v litenote-data:/data litenote-jetstream
API
| Endpoint | Description |
|---|---|
GET /notes?cursor=&limit= |
Paginated notes from all users |
GET /:did/notes?cursor=&limit= |
Paginated notes for a specific DID |
Environment Variables
| Variable | Default | Description |
|---|---|---|
SQLITE_PATH |
notes.db |
Path to the SQLite database file |