[ckan-dev] difference between development.ini and production.ini

Wed Oct 16 12:11:39 UTC 2013

Hi Hilde,

this is simply a way to create a different configuration for your different
environments. Your are free to choose a different name. When running a
paster command or CKAN itself, you just have to specify the path and name
of your configuration file.

Possible use cases are, that you could define, in a development
environment, that you want to log all errors to a log file, whereas you
define to send a mail with all errors when you are running a productive
instance. In your case, it doesn't really matter how this file is called
and it has nothing to do with whether you develop or not.

- Stefan

On Wed, Oct 16, 2013 at 12:56 PM, Hildegard Gerlach <
hildegard.gerlach at jrc.ec.europa.eu> wrote:

> Hello,
>
> when I set up a new CKAN instance and create the CKAN configuration file,
> what is the difference if I create a development.ini or a production.ini
> file ? What does it mean for the CKAN instance ? We are just using CKAN now
> (or testing it), but we are not developping (at least for now).
>
> Thanks
>
> Hilde
>
>
> ______________________________**_________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/**listinfo/ckan-dev<http://lists.okfn.org/mailman/listinfo/ckan-dev>
> Unsubscribe: http://lists.okfn.org/mailman/**options/ckan-dev<http://lists.okfn.org/mailman/options/ckan-dev>
>

-- 
Liip AG  //  Feldstrasse 133 //  CH-8004 Zurich
Tel +41 43 500 39 80 // GnuPG 0x7B588C67 // www.liip.ch
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20131016/22b79397/attachment-0001.html>