Can’t find help in ./flow help for change context from «Development» to «Production».
In Flow-Docu I found lots of information about the meaning and usefulness of context.
In the Production context all caches are enabled, logging is reduced to a minimum and only generic, friendly error messages are displayed to the user (more detailed descriptions end up in the log).
But to be honest, I found not one word about «How change Context» … Obviously, I am totally blind! – Or at least I search at the totally wrong places.
##setEnv FLOW_CONTEXT Production
Have found setEnv.
Is «setEnv» state of the art at «the current neos-level»? Or is this outdated? Don’t like to try and error. Maybe I can’t find «eye - catching changes»…
##httpd-vhosts.conf change not allowed?
On local developing machine in have possibilities to edit the httpd-vhosts.conf.
But on public server managed by hoster most of the time no chance.
Should I set Environment Variables «FLOW_CONTEXT Production» with .htaccess?
is somewhere in backend a check-marker to realize the context-change has done for «default requests»?
A tool for check the cache-behavior (site-wise/nodetype-wise) would be nice: Is there some sort of package/plugin/“enabling neos internals”?
##Handling with httpd-vhosts.conf- or .htaccess-files is not tingling
- Is there also a ./flow-solution that is not documented in help, or which I have overlooked? Or maybe in a area of the neos-administration-backend?