readest-lite
Single-container self-hostable Readest fork with SQLite + local FS, no Supabase or paywall. Features per-user AES-GCM encrypted vaults, quota enforcement, proxy toggle, and full translation/dictionary support.
Ficha actualizada 22 sept 2026, 22:53 · upstream 22 sept 2026, 22:44 · release v8.23.2
Qué es readest-lite
Descripción editorial construida a partir del repositorio, su documentación y sus señales de mantenimiento.
Readest Lite is a single-container, self-hostable fork of the popular reading assistant platform Readest. It replaces the upstream Supabase + R2/S3 storage stack with SQLite for local database persistence and a local filesystem for book files, eliminating cloud dependencies entirely.
The project removes all Pro/paywall features, disables user signup (admin-created via management panel), and implements per-user AES-GCM encrypted vaults that store passwords, API keys, and encryption keys in memory. This ensures complete data isolation between users without requiring external authentication services or paid storage tiers.
Key capabilities include: - Full translation and dictionary support with optional DeepL integration - Remote book downloads via HTTP proxies with SSRF protection - Quota enforcement per user through a configurable admin panel - Proxy toggle that allows direct connections when the server is unavailable - Comprehensive file management including uploads, downloads, sharing, and OCR - Multi-user administration with role-based access (super_admin > admin > user) - Persistent SQLite databases backed by local filesystem storage - Full RSS feed synchronization with CRDT-based replication for conflict-free updates
- Self-hosted reading assistant on a home server or small VPS without cloud dependencies
- Encrypted personal vault for storing passwords, API keys, and sensitive credentials per user
- Offline-first book reader with remote download support via HTTP proxies
- Multi-user collaborative platform where each user has isolated data through AES-GCM encryption
- Translation and dictionary tool that can be integrated into existing reading workflows
- Quota-enforced resource management for shared cloud storage or external services
- Eliminates all cloud dependencies by replacing Supabase with SQLite + local filesystem, enabling true self-hosting on any machine
- Per-user AES-GCM encrypted vaults provide complete data isolation without requiring external authentication infrastructure
- Proxy toggle allows direct connections when the server is unavailable, maintaining full functionality offline
- Full translation and dictionary support including optional DeepL integration with quota enforcement
- Remote book downloads via HTTP proxies with SSRF protection against common web vulnerabilities
- Comprehensive file management system supporting uploads, downloads, sharing, OCR, and multi-format handling
- No built-in user signup — all users must be created through the admin panel, which may not suit fully automated deployments without a dedicated admin interface
- SQLite database is single-threaded by default; concurrent access to the same table can cause race conditions and potential data corruption in high-load scenarios
- AES-GCM encryption keys are stored in memory only (in-memory vault), meaning they must be re-generated on container restart or password change, requiring careful key management
- No native support for cloud storage providers other than local filesystem — S3-compatible services require custom implementation of HMAC-signed URLs
- Quota enforcement is currently managed by an admin panel rather than being enforced server-side at the API level without additional middleware
Perfil de infraestructura
Estimación inicial derivada del repositorio y de los servicios detectados.
Despliegue detectado
Qué señales reales de instalación hemos encontrado.
Deploy Readest Lite using Docker Compose for simplicity. Start with a single container on port 8225, mounting your local data directory to `/data` so that container restarts do not lose user data or book files. For production environments, consider: - Using a reverse proxy (Nginx/Apache) in front of the container for SSL termination and load balancing - Implementing rate limiting on the API endpoints to prevent abuse under high traffic - Configuring environment variables carefully: set `SUPER_ADMIN_EMAIL` equal to `ADMIN_EMAIL` to grant super_admin privileges, or use a dedicated admin account with elevated permissions - For multi-user deployments, ensure each user has their own encrypted vault key stored securely (e.g., in a password manager or secure enclave) - Enable the proxy toggle (`proxyEnabled: true`) when external services are unavailable to maintain full functionality - Monitor
Stack y dependencias
Componentes inferidos a partir de manifests, configuración y documentación.
Puede sustituir a
Relaciones detectadas por el análisis del repositorio y su categoría.
Experiencia real de la comunidad
Ayuda a contrastar la estimación automática con instalaciones reales.
Todavía no hay datos comunitarios para este proyecto.