deprecate configAutoReload

I am considering dropping configAutoReload as it mostly creates contention havoc as it was designed to put the application in first request basis ALL the time. I think this setting does more harm than good. What are your thoughts?

+1, I have never used it.


I’ve never used it, either. Well, other than maybe once or twice way back in 1.x (or was it 2.0?). It’s just way too time consuming for someone with as little patience as me. :slight_smile:

I do know people who use it during development.

Perhaps a better solution could be to write a “Production Checklist” plug-in that scans for common issues like auto reload of the config, singletons, etc…