These CKAN Versions are exactely matched:

• 2.1
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4
• 2.1.5
• 2.1.6
• 2.10.0
• 2.10.1
• 2.10.2
• 2.10.3
• 2.10.4
• 2.10.5
• 2.10.6
• 2.10.7
• 2.10.8
• 2.10.9
• 2.11.0
• 2.11.1
• 2.11.2
• 2.11.3
• 2.11.4
• 2.12.0
• 2.2
• 2.2.1
• 2.2.2
• 2.2.3
• 2.2.4
• 2.3
• 2.3.1
• 2.3.2
• 2.3.3
• 2.3.4
• 2.3.5
• 2.4.0
• 2.4.1
• 2.4.2
• 2.4.3
• 2.4.4
• 2.4.5
• 2.4.6
• 2.4.7
• 2.4.8
• 2.4.9
• 2.5.0
• 2.5.1
• 2.5.2
• 2.5.3
• 2.5.4
• 2.5.5
• 2.5.6
• 2.5.7
• 2.5.8
• 2.5.9
• 2.6.0
• 2.6.1
• 2.6.2
• 2.6.3
• 2.6.4
• 2.6.5
• 2.6.6
• 2.6.7
• 2.6.8
• 2.6.9
• 2.7.0
• 2.7.1
• 2.7.10
• 2.7.11
• 2.7.12
• 2.7.2
• 2.7.3
• 2.7.4
• 2.7.5
• 2.7.6
• 2.7.7
• 2.7.8
• 2.7.9
• 2.8.0
• 2.8.1
• 2.8.10
• 2.8.11
• 2.8.12
• 2.8.2
• 2.8.3
• 2.8.4
• 2.8.5
• 2.8.6
• 2.8.7
• 2.8.8
• 2.8.9
• 2.9.0
• 2.9.0a
• 2.9.1
• 2.9.10
• 2.9.11
• 2.9.13
• 2.9.2
• 2.9.3
• 2.9.4
• 2.9.5
• 2.9.6
• 2.9.7
• 2.9.8
• 2.9.9

ckanext-intro - A quick interactive introduction to writing CKAN extensions

This is a sample extension, intended as a quick and interactive introduction to writing CKAN extensions. It was used in the CKAN workshop at OKCon 2013.

This does not go into as much details as the proper tutorials for writing extensions. Developers willing to start writing CKAN extensions should use those as they provide all necessary detail:

• Writing extensions tutorial: http://docs.ckan.org/en/latest/extensions/tutorial.html
• Custom theming tutorial: http://docs.ckan.org/en/latest/extensions/theming.html

Requisites

• A running source CKAN 2.1 install (http://docs.ckan.org/en/latest/install-from-source.html)
• A sysadmin user
• Some datasets created

Installation

Install the extension as usual, in your activated virtualenv:

pip install -e git+https://github.com/okfn/ckanext-intro.git#egg=ckanext-intro

If you want to jump straight away to the end result, just add the plugin to your CKAN configuration file:

ckan.plugins = intro_plugin

It is recommended though that you follow the individual steps as described in the next section.

How it works

The repository contains a step-by-step process of building an extension. Each step is contained in a single commit, and flagged with a git tag (step1, step2, …)

You can move between steps using the git checkout command. For example to start on the first step:

git checkout step1

To move to the next step:

git checkout step2

And so on.