I think, that the folder structure with logs and cached files inside
the app folder make working with project based editors like Eclipse
PDT / Zend Studio 8 or Netbeans not realy easy.
Some drawbacks of putting the logs and caches inside the app forder
- Building process of IDE is realy slow
- IDS are out of sync everytime you test your application because of
the log-files! (a pain in Zend Studio 8)
- Search takes long time
- Logs and cached files are found in searchresult.
- Maybe problems with version control, if you dont exclude logs, cache
and *.cache and web/bundles
I know, that some of us work with editors without a project based
approach dont have problems with the pain points mentioned above, but
other have!
--
Here my RFC for a filestructure healing these problems in my opinion
project
# mutable contains only generated data
mutable/
app/
cache/
...
logs/
...
bootstrap_cache.php.cache
bootstrap.php.cache
web
asset
acmedemo
# code contains sources
code/
app/
config/
Resources/
AppCache.php
...
console
phpunit.xml.dist
bin/
...
src/
...
vendor/
...
web/
asset -> /path/to/asset/ (symlink)
app.php
...
robots.txt
LICENSE
README.md
VERSION
Andreas
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
