<br><br><div class="gmail_quote">On Mon, Apr 5, 2010 at 2:31 AM, Oleg Kostyuk <span dir="ltr"><<a href="mailto:cub.uanic@gmail.com">cub.uanic@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2010/3/30 Bill Moseley <<a href="mailto:moseley@hank.org">moseley@hank.org</a>>:<br>
><br>
> ..........................<br>
<div class="im">> The applications have separate YAML files for different environments. There<br>
> might be "dev.yml", "testing.yml", "qa.yml", and "produciton.yml". Each<br>
> machine has a file in /etc/<$app_name> that sets what environment the<br>
> application should start in (i.e. what YAML config file to use). Push to<br>
> testing and the app starts and uses the testing database as configured in<br>
> testing.yml.<br>
<br>
</div>Catalyst already have such possibility: read end of "DESCRIPTION" in<br>
Catalyst::Plugin::ConfigLoader, and more details in description of<br>
get_config_local_suffix().<br></blockquote><div><br></div><div>Yes, similar. ConfigLoader didn't exist when I wrote the above, and it's not a plugin (the Plugin is just a thin wrapper) -- it's available outside of Catalyst which is very useful. Wasn't there talk a while back about splitting up ConfigLoader to make it available outside of Catalyst and with the ability to merge files?</div>
<div><br></div><div> </div></div><br>-- <br>Bill Moseley<br><a href="mailto:moseley@hank.org">moseley@hank.org</a><br>