[Feature] Easier setup

[Lure5134]

Feature Description

I would appreciate if the setup would be a bit easier.
The currently recommended docker compose (https://raw.githubusercontent.com/logtide-dev/logtide/main/docker/docker-compose.yml) contains 9 services and 4 volumes.
If I am running just a simple service on a low budget device (e. g. a raspberry) and don't have that much logs it would be nice, if i can start it without to much overload.
For example if instead of redis, mongodb, clickhouse and postgres a simple sqlite could be used if nothing is configured. (The same for the some other services)
This would drastically help in a very simple setup.

Problem/Use Case

The setup seems a bit complicated and a bit overloaded for a simple service.

Priority

• Critical - Blocking my usage of LogTide
• High - Would significantly improve my workflow
• Medium - Nice to have
• Low - Minor enhancement

Target Users

• DevOps Engineers
• Developers
• Security/SIEM Users
• System Administrators
• All Users

Contribution

• I would like to work on implementing this feature

[Polliog]

Hi @Lure5134 thank you for the feedback, and also a point that i need write better inside the documentation.

A couple of things worth noting:

The default docker-compose.yml is already pretty lean. Without any --profile flags, it only starts 5 services: PostgreSQL (TimescaleDB), Redis, the backend, the worker, and the frontend. MongoDB, ClickHouse, and the two Fluent Bit containers are all opt-in via profiles and won't run unless explicitly requested.

If you want to go even lighter, there's docker-compose.simple.yml which removes Redis entirely. The backend falls back to graphile-worker (PostgreSQL-based job queue) and LISTEN/NOTIFY for live tail so you're down to just 3 containers: PostgreSQL, backend, and frontend.

docker compose -f docker-compose.simple.yml up -d

For a Raspberry Pi with low log volume this should work fine. TimescaleDB is just PostgreSQL under the hood and runs well on ARM with modest resources.

Regarding SQLite: this isn't something we're planning to add. Logtide already supports multiple storage backends via@logtide/reservoir (TimescaleDB, ClickHouse, and MongoDB), but SQLite doesn't fit the profile it lacks the time-series capabilities, concurrent write handling, and query patterns that Logtide depends on for log ingestion and aggregation. TimescaleDB on a Raspberry Pi with low volume is already a very lightweight setup.

That said, you've highlighted a real documentation gap the simple compose and the profile system aren't prominent enough. I'll make sure these are better surfaced in the docs and README. Thanks for raising it.

side note: I've just updated it because some new env were not included

[Polliog]

Closed with #183

[Lure5134]

@Polliog Thanks for you help. I am currently setting it up on my server.
I think it would help to add a separate env file for the simple docker compose because not all fields are required.
Nonetheless the simple setup includes 4 services. You missed the worker service.

I will report back, when the services are running. Thank you for all your hard work.

[Lure5134]

I don't know what i am doing wrong but the open telemetry logs aren't coming to logtide.
My setup looks like this (c#)

loggerConfiguration = loggerConfiguration.WriteTo.OpenTelemetry(options =>
        {
            options.Endpoint = "https://[HIDDEN].app";
            options.LogsEndpoint = "/v1/otlp/logs";
            options.Protocol = OtlpProtocol.HttpProtobuf;
            options.Headers = new Dictionary<string, string>
            {
                ["X-API-Key"] = "[HIDDEN]"
            };
        });

If i change the LogsEndpoint to something else logtide logs a 404. With /v1/otlp/logs nothing get's logged.
What I noticed too is that when I stop the container, delete the volume and restart it I am still logged in. Even if there are no users anymore.