Adding support for DBINDEX redis config value in docker compose

[GroondCharge]

Currently, there is no support for adding dbindex config value ($CONFIG['redis']['dbindex']) within compose file. Even in manually updating or setting the value for a container, the changes aren't applied. This fixes the missing option.

[joshtrichards]

Please see:

#2236
#1286

I'm not 100% against this, but the session handler needs to be considered too. It's not clear what the "right thing to do here is".

Personally I'd just avoid dbindex and use dedicated Redis. This is a container environment after all. :-)

[GroondCharge]

Please see:

#2236 #1286

I'm not 100% against this, but the session handler needs to be considered too. It's not clear what the "right thing to do here is".

Personally I'd just avoid dbindex and use dedicated Redis. This is a container environment after all. :-)

#1286 (comment) this becomes a hassle especially, when one'd try to automate deployment. It feels like this would be a nice feature to have available if needed irregardless if it's not optimal for 90% of the cases. However! There is a middle ground imo - prefixes. This would work if you had a redis instance that's running for multiple services or even, if there are multiple NCs connecting to a redis cluster

[GroondCharge]

According to this: nextcloud/server#32203 the prefix for nextcloud is calculated, but then changes when either path, version and/or instanceid would change. If there was a way to make prefix optionally persistent, then these issues would be solved.

[szaimen]

Hi, maybe this helps as reference?
nextcloud/all-in-one#5126

[GroondCharge]

Hi, maybe this helps as reference? nextcloud/all-in-one#5126

Thank you for this, i changed it to configure session locking appropriately, aswell as name for env variable, to match the ones you used