Hey TrevC, just wondering if you made any progress with this or found anything out regarding leaving designer-mode on permanently in a production environment?
It's not really recommended for production and it may have performance impact, as it requires checking a number of files for modification on each page view.
There is a performance overhead for anything involving designing or development, especially with the designer mode as it constantly watches the templates for changes.
It also enables debug mode which does things like query logging and we don't recommend setting that in production.
The way to do it safely if you have to is to only enable designer mode for specific IP addresses. That can be done by wrapping the config in an IP address check.
Ok so it sounds like its pretty tightly coupled with debug mode.
The reason I asked is because we're trying to come up with a way to work on template files through an IDE, have them committed to source control and then deploy those files directly to our server, without having to run an additional database update step.
Is 'loading templates from filesystem with as little additional overhead as possible' a feature that might be supported in the future? Even if we had to have every template stored on the filesystem to skip the database check completely.