Perfect! Thanks Alexander and Carsten! :) On Mon, Oct 29, 2012 at 12:55 PM, Carsten Ziegeler <[email protected]>wrote:
> As Alex explains configurations get a priority, configurations not > bound to a run mode have the lowest priority. Nevertheless all > configurations that apply to the current setup are passed to the > installer, so if you have a configuration for the same server X in a > folder named "config" and "config.dev" and dev is an active run mode, > both are seen by the installer. > > The installer installs the one with the highest priority which in this > case is the one from config.dev. So this one gets the state > "INSTALLED" in the console, and the other one gets the state > "INSTALL". > > Carsten > > 2012/10/29 Alexander Klimetschek <[email protected]>: > > On 29.10.2012, at 16:47, Jakob Külzer <[email protected]> wrote: > > > >> Are /app/foo/config* folders not exclusive or? For example, if I have > >> config and config.dev and the runmodes are "foo,dev", would it not load > >> config.dev only? Or is configuration in "config" (without any runmodes) > >> always selected). > > > > Yes, if you have a "config" folder without any runmode, it is always > considered. However, a specific service configuration in "config.<mode>" > should be preferred over one for the same service pid in "config". The > "config" folder acts as default configuration basically. > > > > Cheers, > > Alex > > > > -- > Carsten Ziegeler > [email protected] > -- Cheers, Jakob
