Hi, well it would make sense to work up a cook book entry for this. also with composer it might become possible to manage multiple versions of the same package on a single server.
that being said .. for our projects we tend to use a dedicated virtual server per app anyway. regards, Lukas On Oct 7, 2011, at 20:01 , ryan weaver wrote: > Hi toudi! > > I think the point is that most people will package Symfony inside each > project. In fact, that's the recommended approach, because then you don't > have to worry about different projects needing different versions of Symfony. > > However, your suggestion is totally fine - we won't bring this into core - > but you're more than welcome to setup your projects so that they each draw > from the same, central Symfony libraries. You've definitely got that > flexibility. > > Thanks! > > Ryan Weaver > US Office Head & Trainer - KnpLabs - Nashville, TN > http://www.knplabs.com > http://www.thatsquality.com > Twitter: @weaverryan > > > On Tue, Oct 4, 2011 at 9:28 AM, toudi <[email protected]> wrote: > hello. i began studying symfony 2 documentation and was under > impression that the distribution one downloads is actually the > project's directory structure. > > wouldn't it be nicer if the web/app*.php file was constructed like > this: > > defined("APPLICATION_ENV") || define("APPLICATION_ENV", > (getenv("APPLICATION_ENV") ? getenv("APPLICATION_ENV") : "prod")); > define("SYMFONY_DIR", "/home/toudi/Symfony/"); // <=== this would be > optional line, see below > > require_once __DIR__.'/../app/bootstrap.php.cache'; > require_once __DIR__.'/../app/AppKernel.php'; > > use Symfony\Component\HttpFoundation\Request; > > $kernel = new AppKernel(APPLICATION_ENV, true); > > and then the small change in app/autoload.php: > > defined("SYMFONY_DIR") || define("SYMFONY_DIR", __DIR__."/../"); > > and of course then the replace of __DIR__.'/../' to SYMFONY_DIR > > Such configuration would be automatically backwards-compatibile with > the one that is avalible for download ( i.e. the whole symfony distro > per project ) but with the advantage of the possibilty to upload > symfony distribution into some shared directory on webserver and > re-use such distribution per project. > > best regards, > toudi. > > -- > 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 > > > -- > 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 Lukas Kahwe Smith [email protected] -- 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
