<div dir="ltr"><div style>On Sun, Mar 10, 2013 at 11:44 AM, David Golden <span dir="ltr"><<a href="mailto:xdg@xdg.me" target="_blank">xdg@xdg.me</a>></span> wrote:<br></div><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="im">On Sun, Mar 10, 2013 at 12:01 PM, Rik Brown <<a href="mailto:rik@rikbrown.co.uk">rik@rikbrown.co.uk</a>> wrote:<br>
>> I think it could be useful if the config would be also accessible. Or is<br>
>> there a reason this would not be a good idea?<br>
<br>
</div>I wouldn't want things like database password to be automatically<br>
available. Then a template bug could cause a huge security hole.<br>
<br>
I think if you want to make config data available in templates, it's<br>
be to do that yourself, explicitly and limit it only to keys you need.</blockquote><div><br></div><div style>Be it good or bad, you can access config with 'settings' keyword in templates. I'm not sure what but some of the variables are removed/hidden in error pages. I'm not sure about them in other areas. </div>
<div><br></div><div>see 'Template Tokens' in <a href="https://metacpan.org/module/Dancer::Template::Abstract">https://metacpan.org/module/Dancer::Template::Abstract</a></div><div><br></div></div></div></div>