Heya - you can provide a separate db & redis instance via DATABASE_URL and REDIS_URL environment variables, checkout this doc. The database & redis are still packaged in the container but won't be use.

Let me know if that works for your use case.

Hi,

that partially solves it, at least to the point that the embedded PostgreSQL won't start if an external database is configured.

When I tested with a separated postgres and valkey (redis fork with open license) the redis still gets started in the container, so I am not sure if the external container was used or not.

After thinking about this, I would still prefer a lightweight container without an embedded database and key-value store.
In my opinion, the microservice design has its benefits here, like the docker project describes it in their documentation.
Following this design principle, this would require to run the zoekt, frontend, backend, database and redis each into their own container which might be a little too much here.

So if it were feasible to build a variant without the external dependencies (database + redis) I would appreciate that to not have to think about embedded dependencies and their licenses and so on.

By the way, are you aware that most people do not consider redis to be open source anymore after their recent license changes (see https://www.google.com/search?q=is+redis+open+source ).