[Feature Request] Configurable Redis DB

[orhtej2]

Is your feature request related to a problem? Please describe.
I'd like to reuse existing Redis instance. This however causes collision as ViTransfer binds to DB 0.

Describe the solution you'd like
I see IORedis already provides db constructor argument, hence forwarding env var like REDIS_DB would be sufficient.

Describe alternatives you've considered
🤷

Additional context
Bare metal install.

[MansiVisuals]

Hi @orhtej2

Added this in the dev branch and the 1.1.3-dev docker image now.

You can now set a REDIS_DB variable to pick the redis database, it defaults to 0 so nothing changes for existing setups. It applies to both the cache and the queues so the whole app moves to whatever index you set, no more collisions when you share redis with other apps.

So just add something like REDIS_DB=3 to your env.

If you want to test it on your bare metal install before 1.1.3 releases just pull mansivisuals/vitransfer:1.1.3-dev. Let me know if it works for you.

Also on the postgres question that came up around the packaging, vitransfer doesnt use any postgres 18 only features. The compose just ships postgres:18-alpine because its the latest, but the schema is plain prisma sql, no merge, no uuidv7, no generated columns and no extensions. The only thing with a version floor is gen_random_uuid() which has been in postgres core since 13, so anything from postgres 13 and up works fine.

Hope that helps!