We use it more and more in web apps to share and separate conf across apps and to share conf between the apache served part of the app and the cronned scripts.
All you have to do is figure out which instance you want, tell Gantry::Conf to retrieve that and it figures out what conf you need. It should be relatively easy to write a little url to instance mapper for your case.
Once it knows the instance, it gives you your conf. That includes sharing with others and having your own. The conf can come from files on the local machine or https requests to a centralized conf server, so apps on different boxes can still share (but then you still need a separate index file on each box). You can even add backends to fish from other sources, like sql databases or LDAP.
Phil
In reply to Re: Is there such an animal as Config::Simple::VirtualHost?
by philcrow
in thread Is there such an animal as Config::Simple::VirtualHost?
by hesco
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |