The deal is that I’m always using a simple Own Server hosting type for local target, instead of using Docker (I just don’t see the need for it in local dev).
But for all non-local targets I’m using Docker.
So when switching from one to another, the package is changing. And it causes Redis to stop working on non-local targets.
I can prevent this if after switching to deploy target, I turn off and on the Redis in target settings.
It is on… but there’s still something changing the package.
@nickneustroev thanks, I think our issue is related but sadly not exactly the same.
I am using docker locally as well. But just like you, the redis packages are cleaned from the package.json at some point.
I just tried what you said (well almost, not in the target settings):
go to production target, turn off and on redis in server connect settings.
Result: it added them to the bottom of the package.json file - perhaps this is a fix and it’ll remain like that.