How anirudhmadaan/typing-diary-backend works
Typing Diary Backend is an Express API for accounts, diary entries, and settings synced across devices. A client sends requests to the API; account routes handle registration and session checks, while diary and settings routes validate and update user data. The server persists shared state in Upstash Redis when configured, or in a local file outside Vercel. The excerpts show these features and persistence logic in server.js; other route details are not independently inspected.
Main entry points: server.js Express API · index.js Vercel Adapter
Components 11
API
- Vercel Adapter
api/index.js - Express API
server.js - Health Routes
server.js
Identity
- Account Routes
server.js - Session Security
server.js
Diary And Settings
- Diary Entries
server.js - Synced Settings
server.js
Persistence
- State Manager
server.js - Local State File
server.js - Upstash Redis
Other components
- API Client
Connections 12
- API Client → Express API: sends requests
README.md - Vercel Adapter → Express API: exports app
api/index.js - Express API → Health Routes: serves routes
server.js - Express API → Account Routes: serves routes
server.js - Express API → Diary Entries: serves routes
server.js - Express API → Synced Settings: serves routes
server.js - Account Routes → Session Security: sets sessions
server.js - Account Routes → State Manager: reads and updates
server.js - Diary Entries → State Manager: reads and updates
server.js - Synced Settings → State Manager: reads and updates
server.js - State Manager → Upstash Redis: reads and writes
server.js - State Manager → Local State File: reads and writes
server.js