Enforce redis.conf settings to all Websites + disabling redis.conf editing

Adrien

Hello,

A way to enforce redis.conf settings to all hosted sites. I would also like to disable client sites from tweaking redis.conf on their own.

What do you think?

JohnB

Adrien There will always be the wonderful and favorite client that tweaks things they know nothing about and breaks things.

Personally I don't mind.... Just like if they go into wordpress and mess up the theme, it can be billable time to fix it so it doesn't really cost you anything. Then again I don't work with customers who would have issue paying me for an hour of time to undo their mistake. If its just click restore I wouldn't charge the first time or if its just occasional.

Depending on if you use a ticketing system or any screen before they can submit a ticket, you could make a knowledge base article that pops up based on redis problem keywords. Just have the correct settings they can copy and paste in that article.

kyzoeadmin

i agree that these default configs would be very handy something in the same way at with th php settings.

Zoinkies

Yea I think it’s a problem not having a global configuration. It’s also horrendously annoying you can’t enable FastCGI Cache and Redis by default with a default WP plug-in.

AdamM

+1
Global settings as it is now with php + ability to disable redis.conf settings editing.

Adam

It's definitely possible to deploy a default redis.conf in the future. I don't know if there's much benefit in preventing users from managing their redis.conf since it's specific to their website and subject to the hard resource limits on the package.

Zoinkies

Adam preventing annoying customers breaking their own configuration that has been painstakingly made to improve performance.

kyzoeadmin

Adam I agree with @Zoinkies disabling the config would prevent accidental mistakes when users try to make their site faster but I also understand your vision.

Maybe it is possible to make this configurable or show a warning message and reset button to empty the conf file.

Darren

If you make the redis.conf file immutable (chattr +i redis.conf), it should prevent the user from editing or removing the file by accident.

Realistically, if a user has access to their own files there will always be the possibility for someone to be able to break their site. Getting the balance right between having having enough guardrails for novice users vs allowing experts to make changes as they wish is a tricky line to walk.

Adrien

Darren Realistically, if a user has access to their own files there will always be the possibility for someone to be able to break their site.

Isn't it the case right now with the ability for each website to set it's own redif.conf settings? Or maybe I misunderstood you.

Darren

I mean in the same way that if someone has access to their own website files, they could edit or remove wp-config.php or their index.php, or make a mistake in their .htaccess; just as easily as making a mistake in the redis.conf.

AdamM

Darren
Redis.conf can be always restore manually and it's not a problem. Right?