I would like to start a discussion on multiple base/root dir support in the HttpKernel\KernelInterface.

The basic idea is that an application can have multiple "app" folders for different layers of configuration, resources etc. In a nutshell; global resources (e.g. app/config/parameters.yml, app/Resources/views).

Hi,

My first thought here: "app/" contains the application-stuff. When you split it even further, what does the other folders contain? If it contains things, that you share between applications, maybe it should be a bundle instead?

I wouldn't share configurations between applications, because I would always fear to change a setting in one app to avoid breaking the other one.

However this seems to be a drastic architecture change as %kernel.root_dir% is pretty much used in each bundle out there. On the other hand... symfony2 is already flexible enough to handle this.

I personally favor this kind of setup over symlink terror. Any thoughts on this? Is it desired? Should I stop all development immediately? (I'm currently working on a proof of concept for the framework bundle).

I think it should be more maintainable for non-automated environments. In automated environments (e.g. capifony) symlinking is not a big deal as there's a single point of entrance for maintenance. However with manual environments there's currently not a single point of entrance and then symlinking becomes less maintainable, imho.

On the other hand symlinking could be (nicely) automated using a composer script handler =/

> "I wouldn't share configurations between applications, because I would always fear to change a setting in one app to avoid breaking the other one."

I would like to start a discussion on multiple base/root dir support in the HttpKernel\KernelInterface.

The basic idea is that an application can have multiple "app" folders for different layers of configuration, resources etc. In a nutshell; global resources (e.g. app/config/parameters.yml, app/Resources/views).