Settings in WUI (extension)

[dread]

Use case

As a ckan administrator I want to easily change options about the CKAN install.

Implementation

• Start storing majority of settings in db
• Have editor for settings as part of admin wui
• Settings are also loaded from pylons ini file on start up (or based on a specific command)

Potential options to show in WUI:

• Default Schema (e.g. default, uk government, others)
• Search caching (on/off)
• License service URL

Depends

• Would be part of ckan-admin section and hence build on ticket:833 (Administrative dashboard)

[thejimmyg]

My opinion is that having configuration in a database is a bad idea.

We are currently considering moving to a system where CKAN is installable using apt-get. Since we're already moving functionality into CKAN extensions, choosing what you want kind of CKAN you would like would then be as simple as chosing the package to install. Configuring it would just be editing the config file.

I don't think this is as relevant as it was 10 months ago. Anyone mind if I change this to wontfix?

[rgrp]

I think this is useful but there may be complexities giving the non-reloading nature of python apps. Have also converted to an extension