<div dir="ltr">Hi Adam<br><div><br>The specific difficulty you mentioned can be solved by <a href="https://help.github.com/articles/ignoring-files/">https://help.github.com/articles/ignoring-files/</a> this is pretty a necessity for github otherwise, sooner or later, one forgets.<br><br></div><div>Best regards Hugh<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 16 February 2015 at 17:24, Adam Witney <span dir="ltr"><<a href="mailto:awitney@sgul.ac.uk" target="_blank">awitney@sgul.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi,<br>
<br>
Thanks for your replies.<br>
<br>
I guess my question was more about any security issue of having the database username/password stored in a text file. And what do people consider best practice for this from a security point of view?<br>
<br>
Thanks<br>
<span class="HOEnZb"><font color="#888888"><br>
Adam<br>
</font></span><span class="im HOEnZb"><br>
<br>
> -----Original Message-----<br>
> From: Octavian Rasnita [mailto:<a href="mailto:orasnita@gmail.com">orasnita@gmail.com</a>]<br>
> Sent: 16. februára 2015 17:10<br>
> To: The elegant MVC web framework<br>
</span><div class="HOEnZb"><div class="h5">> Subject: Re: [Catalyst] Where best to store database connection<br>
> information?<br>
><br>
> Catalyst uses Config::General to read .conf files. If Config::General is<br>
> configured with the option -UseApacheInclude, then you can use an apache<br>
> "include file.conf" in the .conf file to include another file from another<br>
> directory which is not saved by git.<br>
><br>
> Or the option -IncludeDirectories can be also useful so all the files from the<br>
> given directory will be included.<br>
><br>
> --Octavian<br>
><br>
> ----- Original Message -----<br>
> From: "David Schmidt" <<a href="mailto:davewood@gmx.at">davewood@gmx.at</a>><br>
> To: "The elegant MVC web framework" <<a href="mailto:catalyst@lists.scsys.co.uk">catalyst@lists.scsys.co.uk</a>><br>
> Sent: Monday, February 16, 2015 6:22 PM<br>
> Subject: Re: [Catalyst] Where best to store database connection<br>
> information?<br>
><br>
><br>
> > the catalyst configloader can load more then just one file.<br>
> ><br>
> > by default it loads "myapp.conf"<br>
> ><br>
> > if a file named "myapp_local.conf" exists it is loaded aswell.<br>
> ><br>
> > docs:<br>
> > <a href="https://metacpan.org/pod/distribution/Catalyst-Plugin-" target="_blank">https://metacpan.org/pod/distribution/Catalyst-Plugin-</a><br>
> ConfigLoader/lib/Catalyst/Plugin/ConfigLoader/Manual.pod#Using-a-local-<br>
> configuration-file<br>
> ><br>
> > On 16 February 2015 at 15:42, Adam Witney <<a href="mailto:awitney@sgul.ac.uk">awitney@sgul.ac.uk</a>> wrote:<br>
> >> Hi,<br>
> >><br>
> >> I have a Catalyst / DBIx::Class application and I have been storing the<br>
> >> database connection parameters in a config file which is sourced using<br>
> >> MYAPP_CONFIG_LOCAL_SUFFIX. But this seems a bit of a security<br>
> problem<br>
> >> having the main password in a text file like this, especially if it goes<br>
> >> into git.<br>
> >><br>
> >> Is there a recommended or best practice place to store database<br>
> >> connection information?<br>
> >><br>
> >> Thanks for any help<br>
> >><br>
> >> Adam<br>
> >><br>
> >> _______________________________________________<br>
> >> List: <a href="mailto:Catalyst@lists.scsys.co.uk">Catalyst@lists.scsys.co.uk</a><br>
> >> Listinfo: <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst" target="_blank">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst</a><br>
> >> Searchable archive:<br>
> >> <a href="http://www.mail-archive.com/catalyst@lists.scsys.co.uk/" target="_blank">http://www.mail-archive.com/catalyst@lists.scsys.co.uk/</a><br>
> >> Dev site: <a href="http://dev.catalyst.perl.org/" target="_blank">http://dev.catalyst.perl.org/</a><br>
> ><br>
> > _______________________________________________<br>
> > List: <a href="mailto:Catalyst@lists.scsys.co.uk">Catalyst@lists.scsys.co.uk</a><br>
> > Listinfo: <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst" target="_blank">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst</a><br>
> > Searchable archive:<br>
> > <a href="http://www.mail-archive.com/catalyst@lists.scsys.co.uk/" target="_blank">http://www.mail-archive.com/catalyst@lists.scsys.co.uk/</a><br>
> > Dev site: <a href="http://dev.catalyst.perl.org/" target="_blank">http://dev.catalyst.perl.org/</a><br>
><br>
><br>
> _______________________________________________<br>
> List: <a href="mailto:Catalyst@lists.scsys.co.uk">Catalyst@lists.scsys.co.uk</a><br>
> Listinfo: <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst" target="_blank">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst</a><br>
> Searchable archive: <a href="http://www.mail-archive.com/catalyst@lists.scsys.co.uk/" target="_blank">http://www.mail-archive.com/catalyst@lists.scsys.co.uk/</a><br>
> Dev site: <a href="http://dev.catalyst.perl.org/" target="_blank">http://dev.catalyst.perl.org/</a><br>
<br>
_______________________________________________<br>
List: <a href="mailto:Catalyst@lists.scsys.co.uk">Catalyst@lists.scsys.co.uk</a><br>
Listinfo: <a href="http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst" target="_blank">http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst</a><br>
Searchable archive: <a href="http://www.mail-archive.com/catalyst@lists.scsys.co.uk/" target="_blank">http://www.mail-archive.com/catalyst@lists.scsys.co.uk/</a><br>
Dev site: <a href="http://dev.catalyst.perl.org/" target="_blank">http://dev.catalyst.perl.org/</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><a href="http://www.hughbarnard.org" target="_blank">http://www.hughbarnard.org</a><br><a href="http://www.twitter.com/hughbarnard" target="_blank">http://www.twitter.com/hughbarnard</a><br><a href="http://www.big-wave-heuristics.com/" target="_blank">http://www.big-wave-heuristics.com/</a><br><a href="http://www.hackney-environment-network.org.uk/" target="_blank"></a></div>
</div>