[Catalyst] Where best to store database connection information?

[Shantanu Bhadoria]

I generally store my config files in /etc/app_name/config.yml and then I
use MooseX::Singleton to store and YAML::XS to load the config data from
the yml into the app in app_name.pm
HTH,
-Shantanu Bhadoria

On Tue, Feb 17, 2015 at 11:09 PM, Hartmaier Alexander <
alexander.hartmaier at t-systems.at> wrote:

> Note that Catalyst itself doesn't use any config loading,
> Catalyst::Plugin::ConfigLoader does.
> This then uses different config file format modules depending on the
> file extension.
>
>
>
> On 2015-02-16 18:10, Octavian Rasnita wrote:
>
>> Catalyst uses Config::General to read .conf files. If Config::General
>> is configured with the option -UseApacheInclude,
>> then you can use an apache "include file.conf" in the .conf file to
>> include another file from another directory which is not saved by git.
>>
>> Or the option -IncludeDirectories can be also useful so all the files
>> from the given directory will be included.
>>
>> --Octavian
>>
>> ----- Original Message ----- From: "David Schmidt" <davewood at gmx.at>
>> To: "The elegant MVC web framework" <catalyst at lists.scsys.co.uk>
>> Sent: Monday, February 16, 2015 6:22 PM
>> Subject: Re: [Catalyst] Where best to store database connection
>> information?
>>
>>
>>  the catalyst configloader can load more then just one file.
>>>
>>> by default it loads "myapp.conf"
>>>
>>> if a file named "myapp_local.conf" exists it is loaded aswell.
>>>
>>> docs:
>>> https://metacpan.org/pod/distribution/Catalyst-Plugin-
>>> ConfigLoader/lib/Catalyst/Plugin/ConfigLoader/Manual.pod#Using-a-local-
>>> configuration-file
>>>
>>> On 16 February 2015 at 15:42, Adam Witney <awitney at sgul.ac.uk> wrote:
>>>
>>>> Hi,
>>>>
>>>> I have a Catalyst / DBIx::Class application and I have been storing
>>>> the database connection parameters in a config file which is sourced
>>>> using MYAPP_CONFIG_LOCAL_SUFFIX. But this seems a bit of a security
>>>> problem having the main password in a text file like this,
>>>> especially if it goes into git.
>>>>
>>>> Is there a recommended or best practice place to store database
>>>> connection information?
>>>>
>>>> Thanks for any help
>>>>
>>>> Adam
>>>>
>>>> _______________________________________________
>>>> List: Catalyst at lists.scsys.co.uk
>>>> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
>>>> Searchable archive:
>>>> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
>>>> Dev site: http://dev.catalyst.perl.org/
>>>>
>>>
>>> _______________________________________________
>>> List: Catalyst at lists.scsys.co.uk
>>> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
>>> Searchable archive:
>>> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
>>> Dev site: http://dev.catalyst.perl.org/
>>>
>>
>>
>> _______________________________________________
>> List: Catalyst at lists.scsys.co.uk
>> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
>> Searchable archive:
>> http://www.mail-archive.com/catalyst@lists.scsys.co.uk/
>> Dev site: http://dev.catalyst.perl.org/
>>
>
>
>
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*"*
> T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien
> Handelsgericht Wien, FN 79340b
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*"*
> Notice: This e-mail contains information that is confidential and may be
> privileged.
> If you are not the intended recipient, please notify the sender and then
> delete this e-mail immediately.
> *"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"
> *"*"*"*"*"*"*"*"*
>
>
> _______________________________________________
> List: Catalyst at lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive: http://www.mail-archive.com/
> catalyst at lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scsys.co.uk/pipermail/catalyst/attachments/20150218/219f8fe1/attachment.htm>