>________________________________
> From: Luis Muñoz <luisemu...@gmail.com>
>To: catalyst@lists.scsys.co.uk
>Sent: Wednesday, May 16, 2012 5:45 PM
>Subject: [Catalyst] Best practice for configuration file placement
>
>Hi there,
>
>I've failed in locating this question as a FAQ, so I would appreciate some
>guidance.
>
>I've written a Catalyst application that will be deployed in Debian. We want
>to keep config files under /etc/some_app/ so naturally, I would like to add
>this path to the ones to be searched by ConfigLoader. The application's main
>.pm contains:
>
> use Catalyst ( qw/
> ConfigLoader
> # ...
> /
> );
I usually put my non code data under /share and access it like this:
__PACKAGE__->config(
'Plugin::ConfigLoader' => {
file => __PACKAGE__->path_to('share', 'etc'),
},
);
I would think you could build something into the makefile.PL that would copy
this stuff to /etc for production.
John
>
>We'll want to run the application under nginx/FastCGI. I realize that I can
>simply set the environment appropriately in the startup rc script but before
>doing that, I was wondering what would be the "best practice" way to achieve
>this?
>
>Best regards.
>
>-lem
>
>
>_______________________________________________
>List: Catalyst@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@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/
