As of now, the redis image by default starts redis w/o a config. The maintainers says that that's up to users. I thought it makes for redis developers to state their take on it.
Comment From: hpatro
@x-yuri The default configuration might not be the most secure (due to backward compatibility reason) and also lot of configuration needs to updated based on the instance/node memory, usage pattern of clients, etc.
So, I guess the config need to be provided would differ across various setup and dealt with case to case basis.
Comment From: x-yuri
What about sane defaults? After all you provide some configs?
https://redis.io/docs/management/config/
At the moment I bet most users stick to the current defaults. For a host OS that would be what the distributive maintainers supply. And it's safe to assume that that would be close to the configs you provide.
With docker the image comes with no config. So most of the time redis would be used with settings "only recommended for testing and development purposes."
Of course, that's a speculation, but... it sounds like what one would expect. And if you agree, do you think that running with no config by default is okay? Meaning, what's worth, running w/o a config or running w/ some config, that might be not particularly tailored to your case?
Comment From: x-yuri
Let me add a bit more. The configs you provide (example), are they better for production than the default settings (supposedly this ones)? What are the decisions you think you can't make for a user under no circumstances?