[DEPRECATED for ZF2 & Composer] Best practice Zend Framework (ZF) skeleton / base with Doctrine2 integration : High code coverage & build scripts using TDD. Issues section ar e used for project planning (features etc)
But in order to make that work, we'd have to make the entire APPLICATION_PATH writable, which strikes me as overly broad.
Might it be better to have a separate folder for those generated proxies? The build process would create the folder and set it writable.
Of course, it's all somewhat moot at the moment. No proxies are actually generated since our repositories currently query for complete object graphs. But in terms of best practices, it might be worthwhile.
At present, it looks like we set:
in the main
Bootstrap
.But in order to make that work, we'd have to make the entire
APPLICATION_PATH
writable, which strikes me as overly broad.Might it be better to have a separate folder for those generated proxies? The build process would create the folder and set it writable.
Of course, it's all somewhat moot at the moment. No proxies are actually generated since our repositories currently query for complete object graphs. But in terms of best practices, it might be worthwhile.
WDYT?