Where to store application config?
Posted: Wed Mar 11, 2009 2:41 pm
Hi everyone,
I've got a web application server that runs 30 or so separate web applications. All their database credentials and access levels are stored in a central config file. Each separate application loads that file & picks out it's particular database information and access levels.
My question is - do you think it makes more sense to have a central file, or to have each application have it's own config file that stores the database credentials and access levels? I'm noticing as I build more apps, that the design of the new apps is held back a bit by the central file & I'm required to access it in a particular way (particularly - importing a global variable). If each app were silo'd a bit more, I'd have more flexibility to pass that information around as I saw fit.
What do you folks think.
I've got a web application server that runs 30 or so separate web applications. All their database credentials and access levels are stored in a central config file. Each separate application loads that file & picks out it's particular database information and access levels.
My question is - do you think it makes more sense to have a central file, or to have each application have it's own config file that stores the database credentials and access levels? I'm noticing as I build more apps, that the design of the new apps is held back a bit by the central file & I'm required to access it in a particular way (particularly - importing a global variable). If each app were silo'd a bit more, I'd have more flexibility to pass that information around as I saw fit.
What do you folks think.