On 24 February 2014 20:14, Mr User [via Zend Framework Community] < [email protected]> wrote:
> that's the catch i wont to remove the vendor directory i find it some how > messy > You should get used to it, that's how "all the cool kids" are doing it nowadays... > > ok let's start again > > i want in my /var/ directory to have things like this > > config data composer init_autoloader.php module > You want to rename "vendor" to "composer"? That's gonna break stuff for no reason. You can do that though: see https://getcomposer.org/doc/04-schema.md#config (vendor-dir) > > and inside composer i just want these files > > autoload.php autoload_classmap.php autoload_namespaces.php > autoload_psr4.php autoload_real.php ClassLoader.php > It will also contain the dependencies, not just those files... > > > and my /var/www will be the public directory > You should really use symlinks or vhosts instead of replacing /var/www directly > > and of course the zend library is in /usr/includes > That is super-confusing :O > > but for some reason i wasn't able to do that > Yeah, because the skeleton app is not meant to do that. It's still a skeleton app though, so you can manipulate it as it pleases you. I still miss your point though - why is this being done? What's the rationale? The current structure comes from a lot Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/customize-ZF2-tp4661729p4661743.html Sent from the Zend Framework mailing list archive at Nabble.com.
