Q: lightweight use case?

[lukasMega]

Hello,
Thank you for this interesting project.

Is the architecture modular enough to allow running it in a very lightweight setup? Specifically:

• No MongoDB - just SQLite instead
• No Redis

I’m aiming for a small, easy, self-hosted deployment for personal use, with only a Node.js runtime required.

[Seusara]

Based on the current self-hosting docs/docker-compose setup, the answer is no — not out of the box. The self-hosted stack is split into separate producer and consumer services that both connect to MongoDB (MONGO_CONNECTION_STRING), plus Redis credentials configured for both services as well. It's a message-broker-style architecture (events go to a producer, get queued, then a consumer writes them to Mongo), not a single Node process talking to one embedded DB, so swapping in SQLite would mean rewriting the producer/consumer data layer and dropping the queue, not just changing a connection string.

If you just want something small, single-process, and SQLite-backed for personal use, you may be better served by a lighter alternative (e.g. Umami, which does support SQLite) rather than trying to strip Litlyx's architecture down. But if this project's roadmap is heading toward a lightweight/embedded mode, it'd be worth the maintainers confirming here.