Version information
This version is compatible with:
- Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
- Puppet >= 4.0.0 < 7.0.0
Start using this module
Add this module to your Puppetfile:
mod 'landcareresearch-ckan', '6.2.9'
Learn more about managing modules with a PuppetfileDocumentation
CKAN Puppet Module
About
This module installs, configures, and manages ckan.
Customizations such as site logo, about page, license, and
customized css are easily configurable from this module.
The ckan database is automatically backed up every day to
<backup_dir>/ckan_database.pg_dump.
Installation
The module can be obtained from the Puppet Forge. The easiest method for installation is to use the puppet-module tool. Run the following command from your modulepath:
puppet-module install landcareresearch/ckan
Requirements
In order to get all of the dependencies do the following:
- puppet module install landcareresearch-ckan
Other Requirements
- Ubuntu 12.04, 14.04, 16.04 Operating System.
Administration
Once ckan is setup and installed, its necessary to manage the instance through several command line tools.
Create Admin Account
Creating an admin account has been simplified with the use of the following command:
/usr/local/bin/ckan_create_admin.bash <USERNAME> <EMAIL>
Purge Account
CKAN currently doesn't enable automation in purging users. You can easily deactivate a user from the web ui. There is a paster command for marking a user as 'deleted' but that user is still in the system. In order to completely remove (purge) a user from the system, use the following command:
/usr/local/bin/ckan_purge_account.bash <USERNAME>
Backups
In order to backup the entire ckan installation, the database and the file store need to be included in your backup system. The following paths should be backed up.
- <backup_dir>/ckan_database.pg_dump
- /var/lib/ckan/default/resources
- /var/lib/ckan/default/storage
Backup Recovery
In order to recover from a data failure or to just install a new instance do the following as root.
/usr/local/bin/ckan_recover_db.bash
Upgrading ckan puppet module
Its currently unsupported to upgrade between minor versions. For instance version 0.2.x to version 0.3.x. Please see the change log for more details. Its highly recommended to provision a clean system when moving between major and minor versions. Upgrading between build versions can be done on existing systems.
Upgrading CKAN
Upgrading between ckan versions is currently not fully automated via puppet. To upgrade on an existing server, just change the ckan version. After puppet is run with the new ckan version, there are two scripts that can be used after the upgrade.
/usr/local/bin/ckan_upgrade_db.bash
/usr/loca/bin/ckan_upgrade_version.bash
ckan_upgrade_db will upgrade the database schema between versions.
ckan_upgrade_version will create the necessary views.
Classes
See REFERENCE.md for details.
Extensions The following are classes that utilize the ckan modularization framework known as extensions. To fully realize the plugin, puppet needs to be run twice. The first time puppet runs, the extension won't be added to ckan due to how this module manages the plugins.
See REFERENCE.md for details on the ext classes.
Manual Configuration
A systems admin account is still required to be created manually. If using Ubuntu, use the following command:
/usr/local/bin/ckan_create_admin.bash <username>
Module Usage
This section shows example uses of the ckan module.
Example 1
This example demonstrates the most basic usage of the ckan module.
class { 'ckan':
site_url => 'test.ckan.com',
site_title => 'CKAN Test',
site_description => 'A shared environment for managing Data.',
site_intro => 'A CKAN test installation',
site_about => 'Pilot data catalogue and repository.',
plugins => 'stats text_preview recline_preview datastore resource_proxy pdf_preview',
app_instance_id => '{xxxxxxxxxxxxxxxx}',
beaker_secret => 'xxxxxxxxxxxx',
is_ckan_from_repo => 'false',
ckan_package_url => 'http://packaging.ckan.org/python-ckan_2.2_amd64.deb',
ckan_package_filename => 'python-ckan_2.2_amd64.deb',
}
Example 2
This example demonstrates a customize the ckan module.
Declaring a class that manages the configuration files.
class {landcare_ckan::config: }
Declaring the ckan module with the customized parameters.
class { 'ckan':
site_url => 'test.ckan.zen.landcareresearch.co.nz',
site_title => 'Landcare Research Test CKAN Repository',
site_description => 'A shared environment for managing Landcare Research Data.',
site_intro => 'Welcome to the Landcare Research Pilot Data Repository. This is a trial installation of the CKAN software, for us to test ahead of (all going well) a wider company rollout.',
site_about => 'Pilot data catalogue and repository for [Landcare Research] (http://www.landcareresearch.co.nz)',
plugins => 'stats text_preview recline_preview datastore resource_proxy pdf_preview',
app_instance_id => '{xxxxxxxxxxxxxxxx}',
beaker_secret => 'xxxxxxxxxxxx',
site_logo => $landcare_ckan::config::logo_src,
license => $landcare_ckan::config::license_src,
is_ckan_from_repo => false,
ckan_package_url => 'http://packaging.ckan.org/python-ckan_2.2_amd64.deb',
ckan_package_filename => 'python-ckan_2.2_amd64.deb',
custom_css => $landcare_ckan::config::css_src,
custom_imgs => $landcare_ckan::config::custom_images_array,
require => Class['landcare_ckan::config'],
}
Class where the customized configuration files are managed
class landcare_ckan::config {
$img_dir = '/usr/lib/ckan/default/src/ckan/ckan/public/base/images'
$landcare_src = 'puppet:///modules/landcare_ckan'
$css_src = "$landcare_src/custom.css"
$background_img_src = "$landcare_src/LCR-ckan-homepage-background.jpg"
$custom_images_array = [$background_img_src]
$logo_filename = 'lcr_logo_white_sm.png'
$logo_src = "$landcare_src/$logo_filename"
$license = 'NZ_licenses_ckan.json'
$license_src = "$landcare_src/$license"
$backup_dir = '/backup',
}
Deploying with Vagrant
Vagrant can be used to easily deploy the ckan module for testing or production environments. Vagrant was used for the development of the ckan module.
Vagrantfile
The following content should be copied to a clean Vagrantfile. Note, make sure to edit puppet.module_path with a path to where the ckan module and the ckan module dependencies are located.
# -*- mode: ruby -*-
# vi: set ft=ruby :
Vagrant.configure("2") do |config|
config.vm.box = "precise64"
config.vm.box = "ubuntu/precise64"
config.vm.network "private_network", ip: "192.168.33.10"
config.vm.provider "virtualbox" do |v|
v.memory = 2048
v.cpus = 1
end
config.vm.provision :shell, :path => "upgrade-puppet.sh"
config.vm.provision "puppet" do |puppet|
puppet.module_path = "</path to modules>/modules/"
puppet.manifests_path = "manifests"
puppet.manifest_file = "test-ckan.pp"
end
end
test-ckan.pp
This is the file that contains the declaration of the ckan module. The file test-ckan.pp should be created in project_home/manifests/.
class { 'ckan':
site_url => 'http://192.168.33.10',
site_title => 'CKAN Test',
site_description => 'A shared environment for managing Data.',
site_intro => 'A CKAN test installation',
site_about => 'Pilot data catalogue and repository.',
plugins => 'stats text_preview recline_preview datastore resource_proxy pdf_preview',
app_instance_id => '{xxxxxxxxxxxxxxxx}',
beaker_secret => 'xxxxxxxxxxxx',
is_ckan_from_repo => false,
ckan_package_url => 'http://packaging.ckan.org/python-ckan_2.2_amd64.deb',
ckan_package_filename => 'python-ckan_2.2_amd64.deb',
pg_hba_conf_defaults => true,
}
upgrade-puppet.sh
This file manages installing the latest puppet from puppetlabs and updates apt-get The file upgrade-puppet.sh should be created in project_home/ (same directory as the Vagrantfile).
#!/bin/bash
DISTRIB_CODENAME=$(lsb_release --codename --short)
DEB="puppetlabs-release-${DISTRIB_CODENAME}.deb"
DEB_PROVIDES="/etc/apt/sources.list.d/puppetlabs.list" # Assume that this file's existence means we have the Puppet Labs repo added
if [ ! -e $DEB_PROVIDES ]
then
apt-get install --yes lsb-release
# Print statement useful for debugging, but automated runs of this will interpret any output as an error
# print "Could not find $DEB_PROVIDES - fetching and installing $DEB"
wget -q http://apt.puppetlabs.com/$DEB
sudo dpkg -i $DEB
sudo apt-get update
sudo apt-get install --yes puppet
fi
Testing
This module uses the puppet-functional-tester for testing the supported platforms. Please see puppet-functional-tester/README.md file additional information.
Limitations
Only works with debian based OS's.
Development
The module is Free and Open Source Software. Its available on bitbucket. Please fork!
Reference
Table of Contents
Classes
ckan
: Installs, configures, and manages ckan.ckan::ckanapi
: Installs the ckan commandline apickan::config
: Configuration supporting ckanckan::db_config
: Configuration supporting database for ckanckan::ext::archiver
: Installs the archiver extension.ckan::ext::composite
: Installs the composite extension.ckan::ext::dcat
: Installs the dcat extension.ckan::ext::ga_report
: Installs the google analytics report extension.ckan::ext::galleries
: Installs the "galleries" extension.ckan::ext::geoview
: Installs the geoview extension.ckan::ext::googleanalytics
: Installs the "googleanalytics" extension.ckan::ext::harvest
: Installs the harvest extension.ckan::ext::hierarchy
: Installs the "hierarchy" extension from data.gov.uk.ckan::ext::lcrnz
: Installs the Landcare Research extension.ckan::ext::ldap
: Installs the "ldap" extension.ckan::ext::officedocs
: Installs the officedocs extension.ckan::ext::pages
: Installs the pages extension.ckan::ext::pdfview
: Installs the "pdf_view" extensionckan::ext::private_datasets
: This CKAN extension allows a user to create private datasets.ckan::ext::repeating
: Installs the "repeating" extension.ckan::ext::report
: Installs the report extension.ckan::ext::resource_authorizer
: Installs the resource authorizer extension.ckan::ext::restricted
: Installs the restricted extension.ckan::ext::scheming
: Installs the scheming extension.ckan::ext::showcase
: Installs the showcase extension.ckan::ext::spatial
: Installs the "spatial" extension.ckan::ext::viewhelpers
: Installs the viewhelpers extension.ckan::ext::xloader
: Installs the xloader extension.ckan::ext::zippreview
: Installs the zippreview extension.ckan::install
: Installs ckan and related software.ckan::params
: The os specific parameters for ckan installs.ckan::postinstall
: Manages tasks to be performed after the initial install likeckan::redis
: A simple non-configured redis server install for the harvest extension.ckan::repos
: repos for ckan installckan::service
: Manages services for ckanckan::supervisor
: Very simple (barely there) installation of supervisor.
Defined types
ckan::custom_images
: Parses the full path to the image, stores the image tockan::ext
: A type which can be used to install a CKAN extension in the default location.ckan::lang
: Manages installing a non default language.ckan::pip_package
: Install an extra pip module, typically to work around mistakes/limitations in extensions.
Classes
ckan
Install Details: http://docs.ckan.org/en/ckan-2.0/install-from-package.html
Additional features:
- Database can be backed up to <backup_dir>/ckan_database.pg_dump determined by the frequency selected.
COPYRIGHT
GPL-3.0+
Examples
Default Setup
class { 'ckan':
site_url => 'test.ckan.com',
site_title => 'CKAN Test',
site_description => 'A shared environment for managing Data.',
site_intro => 'A CKAN test installation',
site_about => 'Pilot data catalogue and repository.',
plugins =>
text_preview recline_preview datastore resource_proxy pdf_preview',
is_ckan_from_repo => 'false',
ckan_package_url =>
'http://packaging.ckan.org/python-ckan_2.1_amd64.deb',
ckan_package_filename => 'python-ckan_2.1_amd64.deb',
}
Parameters
The following parameters are available in the ckan
class.
site_url
Data type: String
The url for the ckan site.
Default value: 'localhost'
site_title
Data type: String
The title of the web site.
Default value: 'localhost'
server_name
Data type: String
The name for the vhost.
Default value: undef
site_description
Data type: Optional[String]
The description (found in header) of the web site.
Default value: undef
site_intro
Data type: Optional[String]
The introduction on the landing page.
Default value: undef
site_about
Data type: Optional[String]
Information on the about page.
Default value: undef
plugins
Data type: Optional[Array[String]]
Contains the ckan plugins to be used by the installation. Do not include the following plugins as they are defaults and are already included. DO NOT INCLUDE: ['stats','text_view','image_view','recline_view'] @example plugins => ['text_preview','datastore','resource_proxy', 'datapusher']
Default value: undef
app_instance_id
Data type: Optional[String]
The secret password for the app instance . To generate a config file that contains a new password, run the following command: @example 'paster make-config ckan /etc/ckan/default/dev.ini'
Default value: undef
beaker_secret
Data type: Optional[String]
The secret password for beaker. To generate a config file that contains a new password, run the following command. @example 'paster make-config ckan /etc/ckan/default/dev.ini'
Default value: undef
site_logo
Data type: Optional[String]
The source of the logo. Should be specified as puppet:////.png Requires the png file extension.
Default value: undef
license
Data type: String
The source to the json license file. Should be specified as puppet://// and maintained by your module
Default value: 'puppet:///modules/ckan/license.json'
ckan_version
Data type: Optional[String]
Helps identify settings and configuration necessary between the different version of ckan. Valid formats:
- '2.2'
- '2.3'
- eq: 'x.y'
Note, ckan_package_url & ckan_package_filename are not set, than the ckan version will use the package url from ckan.org and the appropriate name.
Default value: undef
is_ckan_from_repo
Data type: Boolean
A boolean to indicate if the ckan package should be installed through an already configured repository setup outside of this module. If using Ubuntu/Deb should be able to do "apt-get install python-ckan" Its the same idea for yum and other package managers.
Default value: false
ckan_package_url
Data type: Optional[String]
If not using a repo, then this url needs to be specified with the location to download the package. Note, this is using dpkg so deb/ubuntu only.
Default value: undef
ckan_package_url_user
Data type: Optional[String]
If the URL is password protected, the user name.
Default value: undef
ckan_package_url_pass
Data type: Optional[String]
If the URL is password protected, the password.
Default value: undef
ckan_package_filename
Data type: Optional[String]
The filename of the ckan package.
Default value: undef
custom_css
Data type: String
The source to a css file used for the ckan site. This replaces the default main.css. Should be specified as puppet://// and maintained by your module. Images used in the custom css should be set in custom_imgs.
Default value: 'main.css'
custom_imgs
Data type: Optional[Array[String]]
An array of source for the images to be used by the css. Should be specified as ['puppet:////','...']
Default value: undef
recaptcha_version
Data type: String
The version of recaptcha. Valid options:
- 1 Older style with a red box. The user enters text
- 2 Newer style that the user clicks on a checkbox (cleaner).
@see recaptcha-version
Default value: '2'
recaptcha_publickey
Data type: Optional[String]
The public key for recaptcha. @see ckan-recaptcha-publickey
Default value: undef
recaptcha_privatekey
Data type: Optional[String]
The private key for recaptcha. @see recaptcha-privatekey
Default value: undef
max_resource_size
Data type: String
The maximum in megabytes a resource upload can be. @see max-resource-size
Default value: '100'
max_image_size
Data type: String
The maximum in megabytes an image upload can be. @see max-image-size
Default value: '10'
max_file_size
Data type: String
This sets the upper file size limit for in-line previews. @see resource-proxy-max-file-size
Default value: '1048576'
large_file_support
Data type: Boolean
Enables large file to be transfered overriding settings like max_file_size. Also configures apache and nginx to support longer timeouts.
Default value: false
datapusher_formats
Data type: String
File formats that will be pushed to the DataStore by the DataPusher. When adding or editing a resource which links to a file in one of these formats, the DataPusher will automatically try to import its contents to the DataStore.
Default value: 'csv xls application/csv application/vnd.ms-excel'
create_unowned_dataset
Data type: Boolean
Allow the creation of datasets not owned by any organization. @see https://ckan.readthedocs.io/en/2.9/maintaining/authorization.html#ckan-auth-create-unowned-dataset
Default value: false
default_views
Data type: Array[String]
Defines the resource views that should be created by default when creating or updating a dataset. From this list only the views that are relevant to a particular resource format will be created. This is determined by each individual view.
Default value: ['image_view','recline_view']
text_formats
Data type: String
Formats used for the text preview. @see http://docs.ckan.org/en/latest/maintaining/configuration.html#ckan-preview-text-formats
Default value: 'text plain text/plain'
json_formats
Data type: String
JSON based resource formats that will be rendered by the Text view plugin @see http://docs.ckan.org/en/latest/maintaining/configuration.html#ckan-preview-json-formats
Default value: 'json'
xml_formats
Data type: String
XML based resource formats that will be rendered by the Text view plugin @see http://docs.ckan.org/en/latest/maintaining/configuration.html#ckan-preview-xml-formats
Default value: 'xml rdf rss'
image_formats
Data type: String
Space-delimited list of image-based resource formats that will be rendered by the Image view plugin @see http://docs.ckan.org/en/latest/maintaining/configuration.html#ckan-preview-image-formats
Default value: 'png jpeg jpg gif'
postgres_pass
Data type: String
The password for the postgres user of the database (admin user).
Default value: 'pass'
ckan_pass
Data type: String
The password for the ckan user of the database.
Default value: 'pass'
pg_hba_conf_defaults
Data type: Boolean
True if use the default hbas and false to configure your own. This module uses postgresql so this setting informs the postgresql module that the hba's should be handled outside of this module. Requires your own hba configuration.
Default value: true
pg_hba_rules
Data type: Optional[Hash]
This is a hash which uses create_resources to create the hba rules. Optional. The hba rules can also be defined outside of this class.
Default value: undef
postgresql_version
Data type: String
The version of postgresql to use.
Default value: $ckan::params::postgresql_version
postgis_version
Data type: String
The version of postgis to use.
Default value: $ckan::params::postgis_version
install_ckanapi
Data type: Boolean
Installs the ckan api if set to true. Also installs a helper script in /usr/bin/ckan/ckanapi.bash which launches ckanapi with the environment setup.
@see https://github.com/ckan/ckanapi
Default value: false
ckan_api_version
Data type: String
The version of the ckan api to install.
Default value: '3.3'
enable_backup
Data type: Boolean
Backs up the database to /backup/ckan_database.pg_dump.
Default value: true
backup_daily
Data type: Boolean
If backups enabled, sets backups to either daily (true) or weekly (false).
Default value: true
backup_dir
Data type: String
The location where backups are stored.
Default value: '/backup'
solr_url
Data type: String
The base url for downloading solr.
Default value: 'http://archive.apache.org/dist/lucene/solr'
solr_url_user
Data type: Optional[String]
If the URL is password protected, the user name.
Default value: undef
solr_url_pass
Data type: Optional[String]
If the URL is password protected, the password.
Default value: undef
solr_download_user
Data type: Optional[String]
The user for downloading solr.
Default value: undef
solr_download_pass
Data type: Optional[String]
The user's password for downloading solr.
Default value: undef
solr_version
Data type: String
The version of solr to install.
Default value: '5.5.3'
solr_schema_version
Data type: String
The version of the solr schema to use. Valid options:
- '1.2'
- '1.3'
- '1.4'
- '2.0'
- 'spatial' - configures solar with the spatial extensions. Only supports bounding box.
- 'spatial-ext' - configures solar with the extended spatial extension. This allows for bounding box, point, and Polygon.
- 'default'
The options correspond to the following structure:
/usr/lib/ckan/default/src/ckan/ckan/config/solr/schema-<solr_schema_version>
The only exception is default which means schema.xml (required as of ckan 2.3).
Default value: 'default'
solr_schema_extra_fields
Data type: Optional[Array]
An array of strings to be included in the schema.
Default value: undef
solr_jts_url
Data type: String
The url to be used to download the jts library for solr spatial ext. Only used if spatial-ext option is set.
Default value: $ckan::params::jts_url
solr_environment
Data type: Optional[Array]
Bash style environment variables passed at the end of the solr server environment.
Default value: undef
locale_default
Data type: String
Use this to specify the locale (language of the text) displayed in the CKAN Web UI.
Default value: 'en'
locales_offered
Data type: Optional[String]
By default, all locales found in the ckan/i18n directory will be offered to the user. To only offer a subset of these, list them under this option. The ordering of the locales is preserved when offered to the user. @see https://docs.ckan.org/en/2.8/maintaining/configuration.html#ckan-locales-offered
Default value: undef
i18n_directory
Data type: Optional[String]
By default, the locales are searched for in the ckan/i18n directory. Use this option if you want to use another folder.
Default value: undef
ckan_storage_path
Data type: String
The location where files will be stored for the file store. Note, this module handles creating the directory; however, ensure the path leading up to the directory has already been created.
Default value: '/var/lib/ckan/default'
display_timezone
Data type: String
By default, all datetimes are considered to be in the UTC timezone. Use this option to change the displayed dates on the frontend. Internally, the dates are always saved as UTC. This option only changes the way the dates are displayed. The valid values for this options can be found at pytz Available from CKAN 2.5+ (has no effect on previous versions).
Default value: 'UTC'
feeds_author_name
Data type: Optional[String]
This controls the feed author’s name. If unspecified, it’ll use ckan.site_id. @see feeds-author-name
Default value: undef
feeds_author_link
Data type: Optional[String]
This controls the feed author’s link. If unspecified, it’ll use ckan.site_url. @see feeds-author-link
Default value: undef
feeds_authority_name
Data type: Optional[String]
The domain name or email address of the default publisher of the feeds and elements. If unspecified, it’ll use ckan.site_url. @see feeds-authority-name
Default value: undef
feeds_date
Data type: Optional[String]
A string representing the default date on which the authority_name is owned by the publisher of the feed. @see feeds-date
Default value: undef
smtp_server
Data type: Optional[String]
The SMTP server to connect to when sending emails with optional port. The format is : @example: smtp.example.com:587 @see smtp-server
Default value: undef
smtp_starttls
Data type: Optional[String]
Whether or not to use STARTTLS when connecting to the SMTP server. @see smtp-starttls
Default value: undef
smtp_user
Data type: Optional[String]
The username used to authenticate with the SMTP server. Example: username@example.com @see smtp-user
Default value: undef
smtp_password
Data type: Optional[String]
The password used to authenticate with the SMTP server. @see smtp-password
Default value: undef
smtp_mail_from
Data type: Optional[String]
The email address that emails sent by CKAN will come from. Note that, if left blank, the SMTP server may insert its own. Example: ckan@example.com @see smtp-mail-from
Default value: undef
email_errors_to
Data type: Optional[String]
An e-mail address to send any error reports to. Example: errors@example.com @see email-errors-to
Default value: undef
email_errors_from
Data type: Optional[String]
The from e-mail address to use when sending any error reports. Example: ckan-errors@example.com @see email-errors-from
Default value: undef
roles_cascade
Data type: Optional[String]
Makes role permissions apply to all the groups down the hierarchy from the groups that the role is applied to. @see roles-cascade
Default value: undef
featured_orgs
Data type: Optional[String]
Defines a list of organization names or ids. Example: 'org_one' @see featured-orgs
Default value: undef
featured_groups
Data type: Optional[String]
Defines a list of group names or group ids. Example: 'group_one' @see featured-groups
Default value: undef
activity_streams_enabled
Data type: Boolean
Turns on and off the activity streams used to track changes on datasets, groups, users, etc @see activity-streams-enabled
Default value: true
activity_streams_email_notifications
Data type: Boolean
Turns on and off the activity streams’ email notifications. @see activity-streams-email-notifications
Default value: false
tracking_enabled
Data type: Boolean
This controls if CKAN will track the site usage. @see tracking-enabled
Default value: false
use_ssl
Data type: Boolean
Enable SSL for the site.
Default value: false
use_google_verification
Data type: Boolean
Enable google verification in the nginx configuration.
Default value: false
use_nagios
Data type: Boolean
Use a /nagios.txt in the nginx configuration file.
Default value: false
google_verification_string
Data type: Optional[String]
The google verification string.
Default value: undef
ssl_cert_path
Data type: Optional[String]
The path to the ssl certificate for nginx.
Default value: undef
ssl_key_path
Data type: Optional[String]
The path to the ssl key for nginx.
Default value: undef
disable_bot_pipl
Data type: Boolean
Disable the piplbot @see https://pipl.com/bot
Default value: false
install_from_source
Data type: Boolean
Install from source instead of package.
Default value: false
source_version
Data type: String
The source version to install.
Default value: '2.7.7'
datapusher_version
Data type: String
The version of datapusher to install if using the source version. Ignored if using packaged version. @see https://github.com/ckan/datapusher
Default value: '0.0.16'
install_datapusher
Data type: Boolean
Controlls if the datapusher should be intalled. Only applicable for the source install because the package install automatically installs the datapusher.
Default value: true
ckan::ckanapi
Additional features:
-
Installs a helper script in /usr/bin/ckan/ckanapi.bash which can be used to call ckanapi directly.
-
See also https://github.com/ckan/ckanapi
ckan::config
details: http://docs.ckan.org/en/ckan-2.0/install-from-package.html
Parameters
The following parameters are available in the ckan::config
class.
backup_dir
Data type: String
The location where backups are stored.
site_logo
Data type: Optional[String]
This sets the logo use din the title bar. Default: undef
Default value: undef
ckan::db_config
Configuration supporting database for ckan
ckan::ext::archiver
Installs the archiver extension.
Parameters
The following parameters are available in the ckan::ext::archiver
class.
ckan_conf
Data type: String
Default value: $ckan::params::ckan_conf
paster
Data type: String
Default value: $ckan::params::paster
ckan::ext::composite
Installs the composite extension.
ckan::ext::dcat
Note, requires the harvest extension.
- See also https://github.com/ckan/ckanext-dcat
Parameters
The following parameters are available in the ckan::ext::dcat
class.
revision
Data type: String
The version of dcat to install from github. Can be a git branch or git label.
Default value: 'v0.0.7'
ckan::ext::ga_report
Requires the googleanalytics extension.
Parameters
The following parameters are available in the ckan::ext::ga_report
class.
revision
Data type: String
The version of dcat to install from github. Can be a git branch or git label.
Default value: 'dga-master'
report_period
Data type: String
The frequency of building period reports.
Default value: 'monthly'
bounce_url
Data type: String
Specifies a particular path to record the bounce rate for. Typically it is / (the home page).
Default value: '/'
ckan::ext::galleries
This extension allows storing and referencing image and video assets.
This extension does not install properly on Ubuntu 12.04.
ckan::ext::geoview
Requirements:
In order for this module to update the default_views parameter, it MUST be declared before the ckan module in the manifests. This will allow all of the variables to be evaulated.
Also, ensure that resource_proxy plugin has been enabled.
Parameters
The following parameters are available in the ckan::ext::geoview
class.
openlayers_viewer_enable
Data type: Boolean
Default value: true
openlayers_formats
Data type: String
A string seperated by spaces. Available formats
- Web Map Service (WMS) wms
- Web Feature Service (WFS) wfs
- GeoJSON geojson
- GML gml
- KML kml
- ArcGIS REST API arcgis_rest
- Google Fusion Tables gft (requires google_api_key)
Default value: 'wms geojson'
openlayers_hide_overlays
Data type: Boolean
Overlays won't be visible by default (only the base layer)
Default value: false
openlayers_hoveron
Data type: Boolean
The feature data popup will be displayed when hovering on.
Default value: true
openlayers_google_api_key
Data type: Optional[String]
The google api key required to render google fusion table resources. @see https://developers.google.com/fusiontables/docs/v1/using#APIKey
Default value: undef
leaflet_geojson_viewer_enable
Data type: Boolean
Default value: true
leaflet_wmts_viewer_enable
Data type: Boolean
Default value: true
ckan::ext::googleanalytics
Sends tracking data to Google Analytics and retrieves statistics from Google Analytics and inserts them into CKAN pages.
You should enable the "googleanalytics" plugin to use this extension.
Parameters
The following parameters are available in the ckan::ext::googleanalytics
class.
id
Data type: String
The Google Analytics tracking ID (usually of the form UA-XXXXXX-X).
account
Data type: String
The account name @example example.com @see https://www.google.com/analytics).
username
Data type: String
Google Analytics username.
password
Data type: String
Google Analytics password.
track_events
Data type: Boolean
Adds Google Analystics Event tracking.
Default value: false
revision
Data type: String
The revision (or version) of the source to checkout with git.
Default value: 'master'
ckan::ext::harvest
Installs the harvest extension.
Parameters
The following parameters are available in the ckan::ext::harvest
class.
revision
Data type: String
The revision to use (a git label or git branch).
Default value: 'v1.1.1'
ckan_conf
Data type: String
Default value: $ckan::params::ckan_conf
paster
Data type: String
Default value: $ckan::params::paster
cron_job
Data type: String
Sets the ensure state of the cron job. Options: the standard options for the ensure parameter.
Default value: 'present'
cron_interval
Data type: String
The minute that cron will run (so will run every hour at the specified minute).
Default value: '5'
cron_warning
Data type: String
Check if there is no previous long running harvester instance, if there is and has been running longer then $WARN seconds complain about it as it might be stuck.
Default value: '21600'
ckan::ext::hierarchy
This extension allows organizations to have parents, and displays them in a tree.
-
Note Untested so probably needs some development effort.
ckan::ext::lcrnz
Requirements:
Installs the following extensions.
- ckan::ext::repeating
- ckan::ext::ldap
The id can be found at the following url: http://<CKAN URL/api/action/organization_show?id=
Parameters
The following parameters are available in the ckan::ext::lcrnz
class.
uri
Data type: Optional[String]
The uri to the ldap server to connect. @example 'ldap://localhost:389'
Default value: undef
base_dn
Data type: Optional[String]
The ldap base dn to use for user authentication. @example 'ou=users,dc=landcareresearch,dc=co,dc=nz'
Default value: undef
source
Data type: String
The source of the git repository for this extension.
Default value: 'http://github.com/okfn/ckanext-lcrnz'
revision
Data type: String
The revision (or version) of the source to checkout with git.
Default value: 'master'
install_ldap
Data type: Boolean
True if the ldap module should be installed and false otehrwise.
Default value: true
install_repeating
Data type: Boolean
True if the repeating module should be installed and false otehrwise.
Default value: true
ldap_revision
Data type: String
The revision (or version) of the ldap extension source to checkout with git.
Default value: 'master'
ldap_source
Data type: String
The source of the ldap extension source to checkout with git.
Default value: 'ofkn'
organization_id
Data type: Optional[String]
If this is set, users that log in using LDAP will automatically get added to the given organization.
Default value: undef
ckan::ext::ldap
Installs the "ldap" extension.
Parameters
The following parameters are available in the ckan::ext::ldap
class.
uri
Data type: String
The uri to the ldap server to connect. @example 'ldap://localhost:389'
base_dn
Data type: String
The ldap base dn to use for user authentication. @example 'ou=users,dc=landcareresearch,dc=co,dc=nz'
search_filter
Data type: String
The filter for searching through identities in ldap.
Default value: 'uid={login}'
username
Data type: String
The user name to use as a lookup.
Default value: 'uid'
email
Data type: String
The field that contains the user's email address.
Default value: 'mail'
fullname
Data type: String
The field that contains the user's full name.
Default value: 'cn'
organization_role
Data type: String
The role of the user when logged in through ldap.
Default value: 'member'
organization_id
Data type: Optional[String]
If this is set, users that log in using LDAP will automatically get added to the given organization.
To create the organisation specified in ckanext.ldap.organization.id use the paste command:
paster --plugin=ckanext-ldap ldap setup-org -c
/etc/ckan/default/development.ini
Default value: undef
revision
Data type: String
The revision of the ldap repository.
Default value: 'master'
source
Data type: Enum['ofkn','history']
The source version of the ldap respository.
Default value: 'ofkn'
use_fallback
Data type: Boolean
true if the system should use the ckan database for user authentication if LDAP auth fails.
Default value: false
ckan::ext::officedocs
For this extension to work, the documents to be previewed must be accessible to the wider internet, and will only work if you use a hostname, and not just an IP address.
Parameters
The following parameters are available in the ckan::ext::officedocs
class.
ckan_conf
Data type: String
Default value: $ckan::params::ckan_conf
paster
Data type: String
Default value: $ckan::params::paster
ckan::ext::pages
Installs the pages extension.
ckan::ext::pdfview
If you want to enable pdf views of documents outside of the ckan instance, you will need to enable resource_proxy plugin.
ckan::ext::private_datasets
Only certain users will be able to see. When a dataset is being created, it's possible to specify the list of users that can see this dataset.
Parameters
The following parameters are available in the ckan::ext::private_datasets
class.
show_acquire_url_on_create
Data type: Boolean
To show the Acquire URL when the user is creating a dataset.
Default value: false
show_acquire_url_on_edit
Data type: Boolean
To show the Acquire URL when the user is editing a dataset
Default value: false
ckan::ext::repeating
This extension provides a way to store repeating fields in CKAN datasets, resources, organizations and groups.
ckan::ext::report
Installs the report extension.
Parameters
The following parameters are available in the ckan::ext::report
class.
ckan_conf
Data type: String
Default value: $ckan::params::ckan_conf
paster
Data type: String
Default value: $ckan::params::paster
ckan::ext::resource_authorizer
Installs the resource authorizer extension.
Parameters
The following parameters are available in the ckan::ext::resource_authorizer
class.
ckan_conf
Data type: String
The path to the ckan configuration file.
Default value: $ckan::params::ckan_conf
paster
Data type: String
The paster command to use.
Default value: $ckan::params::paster
ckan::ext::restricted
Installs the restricted extension.
ckan::ext::scheming
Installs the scheming extension.
Parameters
The following parameters are available in the ckan::ext::scheming
class.
source
Data type: Optional[String]
The URL of the remote VCS repository. If undef, uses "http://github.com/ckan/ckanext-scheming".
Default value: undef
revision
Data type: String
The tag or branch to use for the scheming extension.
Default value: 'master'
plugins
Data type: Array[String]
An array of strings that are plugins to add to the plugin configuration in the production.ini. @example ['scheming_datasets','scheming_groups','scheming_orginizations']
Default value: ['scheming_datasets']
data_schemas
Data type: String
The relative path based on a module or a full path that contains the dataset schema. Can be json or yaml. @example 'ckanext.scheming:/usr/lib/ckan/default/src/ckanext-quavonz/ckanext/quavonz/schema/dataset.yml'
Default value: 'ckanext.scheming:ckan_dataset.json'
presets
Data type: String
The relative path based on a module or a full path that contains the preset definitions. Can be json or yaml.
Default value: 'ckanext.scheming:presets.json'
dataset_fallback
Data type: Boolean
The documentation doesn't define this variable but providing for completeness.
Default value: false
ckan::ext::showcase
Installs the showcase extension.
ckan::ext::spatial
Allows for the association of datasets with geographic locations, and for searches across datasets to be restricted to a particular geographical area. Additionally, it provides some support for previewing geographical datasets.
Parameters
The following parameters are available in the ckan::ext::spatial
class.
template
Data type: String
The name the template that spatial will modify. Note, this will overwrite the following files:
- templates/package/search.html
- templates/package/read_base.html
map_provider
Data type: String
Which map provider to use. Options:
- 'default' - removes older configuration which may not work with newer versions of ckanext-spatial.
- 'openstreetmap' - the older settings which may not work due to cross-origin error.
- 'mapquest' - depricated, do not use
- 'custom' - uses a custom type that requires the map_url parameter.
Default value: 'default'
map_type
Data type: Optional[String]
Depricated, no longer used.
Default value: undef
map_url
Data type: Optional[String]
The tileset URL. This follows the Leaflet URL template format ( {z} for zoom and {x} {y} for tile coordinates)
Default value: undef
map_attribution
Data type: Optional[String]
The attribution for the map tiles and license. This expects html formatting for urls like <a href=>.
Default value: undef
default_extent
Data type: Optional[String]
Sets the default extent for the map. Should be a string in the format:
'[[15.62, -139.21], [64.92, -61.87]]'
or GeoJSON
'{ \"type\":
\"Polygon\", \"coordinates\": [[[74.89, 29.39],[74.89, 38.45], [60.50,
38.45], [60.50, 29.39], [74.89, 29.39]]]}'
If undefined, will not set an extent.
Default value: undef
non_extra_spatial
Data type: Boolean
Set to false if the spatial field is not in the extra dictionary.
Default value: false
revision
Data type: Optional[String]
The version of spatial to install.
Default value: undef
add_spatial_search_widget
Data type: Boolean
True if the spatial search should be added and false otherwise.
Default value: true
ckan::ext::viewhelpers
Installs the viewhelpers extension.
ckan::ext::xloader
Installs the xloader extension.
Parameters
The following parameters are available in the ckan::ext::xloader
class.
formats
Data type: String
The formats that are accepted to be uploaded.
Default value: 'csv application/csv xls application/vnd.ms-excel'
revision
Data type: String
The version of the module to install.
Default value: 'master'
ckan::ext::zippreview
Installs the zippreview extension.
ckan::install
Installs ckan and related software.
ckan::params
GPL-3.0+
ckan::postinstall
initializing the database
ckan::redis
There's too many redis modules in the forge to make a good assessment or to enforce the use of any particular one of them for CKAN. Enhancement possibilities exist in making this optional in the harvest module (e.g. supply your own).
Examples
include ckan::redis
ckan::repos
repos for ckan install
ckan::service
Manages services for ckan
ckan::supervisor
This is used to run/manage background permanent tasks, e.g. for harvester jobs etc.
See also ckan::supervisor::program for deploying programs run by supervisor
And some use of ckan::supervisor::program (see that define for details)
Defined types
ckan::custom_images
the ckan_img_dir
ckan::ext
The ext directory classes utilize the ckan modularization framework known as extensions. To fully install the plugin, puppet needs to be run twice. The first time puppet runs, the extension won't be added to ckan due to how this module manages the plugins.
Parameters
The following parameters are available in the ckan::ext
defined type.
extname
Data type: Optional[String]
The name of the extension. Defaults to $title.
Default value: undef
provider
Data type: String
The name of the VCS repository provider where the extension is hosted. Can be any provider supported by puppetlabs/vcsrepo. Defaults to 'git'.
Default value: 'git'
source
Data type: Optional[String]
The URL of the remote VCS repository. Defaults to "http://github.com/ckan/ckanext-$extname".
Default value: undef
revision
Data type: String
The revision of the VCS repository to check out and install.
Default value: 'master'
branch
Data type: String
The branch of the VCS repository to check out and install.
Default value: 'master'
plugin
Data type: Optional[Array[String]]
An array of strings that are plugins to add to the plugin configuration in the production.ini.
Default value: undef
views
Data type: Optional[Array[String]]
An array of string that are views to add to the view configuration in the production.ini.
Default value: undef
pip_requirements
Data type: String
The name of the requirements pip file to be installed. Only the name of the file which is found in the root directory of ext.
Default value: 'pip-requirements.txt'
user
Data type: Optional[String]
Uses the user's $HOME/.ssh setup
Default value: undef
run_setup
Data type: Boolean
Many extensions require the python setup.py develop command to be issued. For convience, this has been added as a default feature which has been disabled. Simply set this to true to run the setup.py command.
Default value: false
run_setup_param
Data type: String
The paramter for the setup.py command.
Default value: 'develop'
ckan::lang
This class expects a zip file that has the contents of the language. The contents of the zip file should have the following:
- LC_MESSAGES/ckan.mo
- LC_MESSAGES/ckan.po
Parameters
The following parameters are available in the ckan::lang
defined type.
url
Data type: String
The url to the language build. The build is a zip file with a root directory.
language
Data type: String
The language that is to be installed.
Default value: $title
web_user
Data type: Optional[String]
The web user to use if authentication is necessary.
Default value: undef
web_password
Data type: Optional[String]
The web user's password if authentication is necessary.
Default value: undef
ckan::pip_package
Install an extra pip module, typically to work around mistakes/limitations in extensions.
Parameters
The following parameters are available in the ckan::pip_package
defined type.
version
Data type: Optional[String]
Specify the version of the package. Note, its advised to leave as undef.
Default value: undef
CKAN Puppet Module Changelog
2022-06-17 Release 6.2.9
- Added a new configuration parameter for setting favicon.
2022-06-15 Release 6.2.8
- Added a new configuration parameter for specifying facet search default value.
2022-06-09 Release 6.2.7
- Added parameter for adding a list of fields in the schema.
- Updated global formatting to meet new puppet lint standards.
- Replaced legacy facts with $facts variable and associated hashes.
- Changed feeds parameters to optional strings.
- Defined missing types for class parameters.
2022-05-31 Release 6.2.6
- Added a parameter to the spatial extension for disabling the spatial widget.
2022-05-31 Release 6.2.5
- Added a param for controlling if a dataset can be created without an organisation.
2022-04-21 Release 6.2.4
- Fixed the created admin script.
2022-02-15 Release 6.2.2 & 6.2.3
- Added additional parameter to language downloads.
2022-02-15 Release 6.2.1
- Fixed an error with selecting the python version.
2022-02-15 Release 6.2.0
- Zipreview's default branch changed to Develop.
- Added python 3 support.
- Added Ckan version 2.9 support.
2021-12-13 Release 6.1.19
- Added solr environment variable.
2021-11-24 Release 6.1.18
- Updated dependencies.
2021-11-10 Release 6.1.17
- Added support for Solr Version 6.5.0 to 6.6.6. Solr Version 7 and 8 do not work due to text_general field type.
- Added new parameters for GA Reports.
2021-09-17 Release 6.1.16
- Added flag in lcrnz extension for disabling repeating extension.
- Added a revision parameter for the spatial extension.
- Fixed a few variables that were mispelled causing warnings.
- Added additional dependancies for ldap extension.
2021-09-17 Release 6.1.15
- Fixed a bug in the create_admin script.
- Preparing Harvester for ckan version 2.9+
- Enabled a switch to turn off ldap from lcrnz extension.
2021-04-12 Release 6.1.14
- Fixed an error in the documentation causing invalid an issue when the references documentation is created.
2021-04-12 Release 6.1.13
- Added additional parameters to ckanext-spatial to allow for custom basemaps and attribution.
2021-04-07 Release 6.1.12
- Updated ckanext-scheming allowing for arbitary sources to be used instead of the default git repository.
- Cleaned up ckanext-scheming paramter list including missing documentation.
- Added ext modules to the API Reference.
2021-03-31 Release 6.1.11
- Added a parameter to ckanext-spatial that allows for checking the spatial field in any dictionary (not just the extra dictionary).
2021-03-29 Release 6.1.10
- Updated the JTL library for solr-spatial-field. Note, I wasn't able to get the solr-spatial-field working, so for now, follow the recomendation of using solr. You can calculate the bounding box automatically with a validator. This is demonstrated by the ckanext-quavonz validator.py
- Changed the default version of geoview to the master branch.
- Added a default for map_provider that uses the default openstreetmaps removing old configuration that no longer works.
- Fixed the URL download path for jts library.
- Updated version of mmseg4j for spatial-ext to enable 'points' for spatial search.
2021-03-25 Release 6.1.9
- Added a parameter for ldap extension to fallback and use ckan database if auth fails ldap.
2021-03-22 Release 6.1.8
- Changed default version of ckanext-scheming.
- Updated create admin script to promote existing users to have admin accounts.
- Using activate when installing extensions.
2021-03-18 Release 6.1.7
- Fixed an issue with the no ssl version of the nginx configuration.
- Added redis server is required and has been added.
- Fixed an issue with ldap only using master branch.
- Updated dependencies.
- Migrated to puppet-functional-tester for managing the functional tests.
2021-02-22 Release 6.1.6
- Added a parameter to allow for large files to be uploaded into CKAN.
2021-02-11 Release 6.1.5
- Changed the limits on proxy timeout.
- Changed the temp directory for storing nginx body contents.
- Added parameters for using credentials to download packages for solr and ckan.
2021-01-11 Release 6.1.4
- Added the package python-future to be installed to fix an issue with xloader.
- Added supervisor as a default service instead as optional.
2020-12-07 Release 6.1.3
- Added configuration to install ckan api versions.
2020-12-07 Release 6.1.2
- Added a configuration setting to the ext defined type to execute python setup.py develop which is a common requirement for extensions.
2020-12-03 Release 6.1.1
- Fixed a bug installing the ldap plugin.
2020-12-03 Release 6.1.0
- Added support for Ubuntu 18.04 (source installs only)
2020-11-25 Release 6.0.7
- Changed the installation of nodejs/npm to use the defaults by the controlling puppet module.
2020-09-04 Release 6.0.6
- Added revision and source to the ldap module. As there are 2 different git repositories that can be used. The repos are ofkn and NaturalHistoryMuseum.
2020-08-25 Release 6.0.5
- Added support for ckan 2.8.
- Updated the nodejs version requirements.
- Changed ldap extension source repository from okfn to NaturalHistoryMuseum.
- Removed support for Ubuntu 14.04.
Known issues
- Datastore still has errors.
- No support for Ubuntu 18.04 as there are issues with the nodejs puppet module.
2020-08-11 Release 6.0.4
- Added schema for restricted scheming to fill out data creation menus.
2020-07-23 Release 6.0.3
- Fixed an issue with the restricted extension's schema.
2020-05-11 Release 6.0.2
- Updated documentation.
- server_name is now a required parameter.
- Updated vagrant testing suite.
- Apache now purges configurations not supplied by this module.
- Added xloader extension but not fully tested.
- Added a parameter for disabling datapusher for source install only.
- Added datastore configuration for source installation.
2020-05-11 Release 6.0.1
- Added installing by source where default was installing by package.
2020-04-29 Release 6.0.0
- Added a solr parameter to include the elevate.xml required for ckan and solr. This parameter was added in solr 0.8.0 as by default, the elevate.xml was copied over, but later version of solr do not include elevate.xml. This may need to be revisted when upgrading past solr version 7.x. Currently, solr version 5.x is recommended for ckan.
- Added composite ext (recommended for restricted ext).
- Added scheming ext (recommended for restricted ext).
- Updated to comply with Puppet Version 6.
- Replaced Anchor patter with contains.
- Changed the formatting of the contributors file.
- The restricted extension has not been verified to work correctly, so consider this extension as expiremental.
2020-01-23 Release 3.1.1
- Added restricted and resourceauthorizer ckan extensions.
2020-01-07 Release 3.1.0
- wget pupet module has been depricated, so wget puppet module has been replaced by Archive.
- Changed dependency for nodejs puppet module.
- Updated vagrant development environment.
- Fixed an issue with array concatination with geoview extension.
- Bounded all dependencies in metadata file.
- Updated dependencies in the vagrant test suite.
2019-10-14 Release 3.0.3
- Changed from using check_run to psql command with unless clause which is more reliable.
- Added 'uploads' directory in the storage path.
2019-10-14 Release 3.0.2
- Changed file permissions on lang directory (a fix for 2.7.6 which seems to require writable permissions to world).
- Fixed changelog formatting to comply with markdown linting.
- Fixed readme formatting to comply with markdown linting.
2019-06-13 Release 3.0.1
- Added a param to block PiplBot in nginx configuration.
2019-01-17 Release 3.0.0
- Upgraded to latest version of postgis module.
- Added param for setting postgresql version .
2018-11-01 Release 2.7.9
- Fixed an issue with ext's using vcsrepo
2018-11-01 Release 2.7.8
- Updated license in metadata.
2018-11-01 Release 2.7.7
- Changed the ext to use 'latest' to pull git repositories.
- Added the requirements section in the meta data.
2018-09-25 Release 2.7.6
- Changed Source URL to use https protocol.
- Changed formatting in change log.
2018-09-25 Release 2.7.5
- Added revision parameter to harvest extension.
- Updated dcat plugin module configuration.
- Removed redis server package from required packages as it was already included in redis extension.
2018-06-27 Release 2.7.4
- Added parameter parsing to the ckan_create_admin script.
- Added required email parameter for ckan_create_admin script.
2018-06-25 Release 2.7.3
- Changed the permissions on extension source directory.
- Added types to the ckan::ext class.
- Added user parameter to the ckan::ext class to use with vcsrepo.
2018-06-20 Release 2.7.2
- Removed types from readme.
- Cleaned up a variable name.
2018-06-20 Release 2.7.1
- Changed a parameter in ext::lcrnz to be optional.
2018-06-20 Release 2.7.0
- Added support for SSL (nginx).
- Fixed directory permissions for language support.
- Added parameter types.
- Changed documentation style to use Puppet Strings.
- Added REFERENCE.md for class and type documentation based on Puppet Strings.
- Removed Preview loadable parameter as it was deprecated as of ckan 2.3.
2018-01-23 Release 2.6.10
- New version of solr puppet module which uses OpenJDK instead of oracle.
2018-01-17 Release 2.6.9
- Added the zip preview extension support
2017-12-06 Release 2.6.8
- Added support for ckan 2.7
- Added support for solr 6.5.1 which requires the ckan/lib/search/init.py file in order to change schema.xml to managed-schema
- Support for Ubuntu 16.04.
2017-09-25 Release 2.6.7
- Changed wget from a class declaration to an include statement to allow for wget to be used in other puppet modules.
2017-07-05 Release 2.6.6
- Added revision for google analytics extension.
2017-05-16 Release 2.6.5
- Added max_file_size parameter.
- Added activity_streams_enabled & activity_streams_email_notification parameters.
- Added tracking_enable parameter.
- Added image_formats parameter.
- Updated readme with new parameters and links to configuration documentation.
2017-04-28 Release 2.6.4
- Added 2 new configuration parameters.
- Deleted undef variables in ckan::params
- Removed deleted variables in init.pp and replaced with undef.
2017-04-10 Release 2.6.3
- ckan verison 2.6 checks the schema version in the schema.xml file. By changing the version to 2.3, the check schema version error is fixed.
2017-04-10 Release 2.6.2
- Added the ability to install languages in the default directory.
2017-04-5 Release 2.6.1
- Updated solr puppet module version
- Updated systemd puppet module version
- Updated postgis version for Ubuntu 16.04
2017-04-05 Release 2.6.1
- Added new dependencies for ckan 2.6
- Moved git-core to required packages from its own declaration in install.pp
- Added a new type called lang which allows the installation of languages.
2017-03-15 Release 2.6.0
- Added support for CKAN version 2.6
- Changed from python-software-properties to software-common-properties
- Changed the default URL from latest to archive for downloading solr
- Changed default version of solr to 5.5.3
- Tested with Puppet 4
2017-01-25 Release 2.5.1
- the pdfview ext now adds pdf_view to the default_view parameter.
2017-01-25 Release 2.5.0
- Added views so that officedocs extension manages both plugins and views.
- Reworked views so that 'default_views' requires an array not a string.
- Fixed issues with geoview related to default_views
2017-01-23 Release 2.4.2
- Added the office docs extension.
- Fixed an issue with galleries ext not installing properly.
2016-12-23 Release 2.4.1
- Added a dependancy to puppetlabs/inifile
2016-12-20 Release 2.4.0
- Removed datastore extension. Just set datastore as a plugin as there is no extra work required to enable datastore.
- Fixed a spelling error in the hide_overlays parameter in geoview extension.
- Replaced puppet template code with the puppetlabs inifile types.
- Converted all extensions to use the new inifile puppet module
- Removed urls that use the git protocol and changed to http protocol.
- Fixed a bug with ckan::pip_package anchor naming
- Added a new parameter for setting the roles cascading.
2016-11-29 Release 2.3.3
- Custom facts have been used to auto populate the ckan.plugins configuration parameter based on ckan::ext. However, in later version of factor, this seems to be unreliable especially when running from Vagrant. This version removes custom facts completely. The mechanism still uses the /etc/ckan/plugins.out file for collecting the plugins and requires 2 puppet runs to enable the plugins in the ckan service. However, this solution will work consistently.
2016-11-18 Release 2.3.2
- The latest version of the postgresql puppet module 4.8.0 has changed their internal dependency structure with the apt puppet module. This has caused the dependency cycle issue because there was dependencies between the landcareresearch/solr module and eventually the puppetlabs/postgresql module. This build decouples those two modules completely.
2016-11-02 Release 2.3.1
- Added new dependencies based on updated version of solr puppet module including systemd, and java8
2016-11-02 Release 2.3.0
- Fixed potential dependency cycle with newer versions of postgresql puppet module.
- Upgraded the solr module version to 0.5.x. Do not use version 2.3.0 with existing ckan instances as this will most likely cause errors with the solr installation. the Solr 0.5.x puppet module now manages solr uses tarballs and not packages. This is an improvement but means that legacy systems will have problems upgrading.
2016-11-02 Release 2.2.7
- Added a cron job for to ensure harvest runs periodically.
- Updated docs to reflect additional parameters on the harvest ext.
2016-07-23 Release 2.2.6
- Added parameters for managing the smtp service. Note, this does NOT install an smtp service.
2016-07-15 Release 2.2.5
- Fixed an error in the spatial ext template.
2016-07-15 Release 2.2.4
- Mapquest is no longer serving tiles via the api used by spatial extension. So a feature has been added to use open street map tiles.
- Discovered that galleries extension doesn't install properly on Ubuntu 12.04 so updated documentation.
2016-07-11 Release 2.2.3
- Added the galleries extension
- Added a global parameter for specifying the ckan packaged python library
2016-07-07 Release 2.2.2
- Added a new class for installing redis for the harvest ext.
- Added missing ext classes documentation from readme.
- Added links to each ext class github repo.
- Removed Authors field in source file headers (as this promotes more of a community). Using contributors.txt is a better way.
2016-07-06 Release 2.2.1
- Fixed a typo in a require statement
- Fixed geoview ext's configuration providing order and white space.
2016-06-23 Release 2.2.0
- Added a parameter for the sender email.
- Added a parameter for the receiver email.
- Added a missing file source.
- Added a missing template.
- Updated documentation for modules.
- Updated readme (partial).
2016-06-22 Release 2.1.15
- Added a parameter for managing the directory for database backups and restores.
- Fixed a configuration problem with spatial search.
- Fixed a bug where an exec runs every puppet run (wsgi_create).
- Fixed a bug for the location of the paster command.
2016-06-21 Release 2.1.14
- Added geoview extension
2016-05-03 Release 2.1.13
- Fixed spatial search problem with templates.
2016-04-27 Release 2.1.12
- Changed from using the ckan python pip to the system packaged pip.
- Added installation of python2.7 and python-pip for deb versions.
2016-04-27 Release 2.1.11
- Added a parameter to change the postgis version.
2016-04-22 Release 2.1.10
- Added support for ckan version 2.5.
2016-04-18 Release 2.1.9
- A bug was discovered with the automatic backups. If the spatial extension was enabled than backups would fail. This bug has been fixed.
2016-03-29 Release 2.1.8
- Added a new extension called private dataset
- Added vagrant testing environment
- Handling nodejs for Ubuntu 12.04 and 14.04
2016-01-11 Release 2.1.7
- Added parameters to change the source repo for the lcr extension.
2015-12-09 Release 2.1.6
- Added ckan_upgrade_db.bash
- Added ckan_create_views.bash
- Added ckan_purge_account.bash (uses expect package)
- Added recaptcha version. Changed the default to 2 instead of 1.
- Fixed postgresql ppa problem bug.
- Added Ubuntu 14.04 support.
- Updated the solr default version to 5.3.0
2015-10-30 Release 2.1.4
- Added the json_formats and xml_formats for the configuration file.
- Text Formats will always be added to configuration.
- Changed recaptcha public/private defaults to undef.
- Updated for future parser compliance (puppet 4)
2015-09-xx Release 2.1.0
- Added support for ckan version 2.3
- Added default_locale param for ckan configuration
- Added ckan.i18n_directory param for ckan configuration
- Added support for 2.3 changes like preview vrs new view system
- Upgraded Landcare Research ext to lcrnz
- Added repeating extension
- Added ldap extension
- Enabled the storage path of the file store to be set by module.
- Updated to using Solr 5.x
- Enabled both solr and solr-spatial-field for the backend to spatiel search.
2015-04-02 Releaes 2.0.1
- The changed to using the postgresql password hash function.
- Added ckan version specifing the version of ckan to use.
2015-03-23 Releaes 2.0.0
NOTE
Due to a change of how the database is initialized, upgrading from previous version of this module will re-initialize your database!!!! This means, you need to backup the database before doing this upgrade.
To recover your database use the following command (make sure you sudo su first)
paster --plugin=ckan db clean --config=/etc/ckan/default/production.ini ckan_database.pg_dump
paster --plugin=ckan db load --config=/etc/ckan/default/production.ini ckan_database.pg_dump
- Added the landcareresearch/solr puppet module.
- Tested with solr 4.10.3.
- Database initialization is now moved to a bash script in /usr/local/bin
- Added a solr schema parameter that instructs which schema version to use.
2015-03-04 Release 1.0.13
- Migrated from github to bitbucket
- Changed ownership of puppetforge account
- Added openhub badge to readme.
- Migrated changelog into md format.
- Changed ckan_run dependancy to landcareresearch account.
- Output of new CKAN Fact now correctly reports if the /etc/ckan/plugins.out file doesn't exist.
2015-02-16 Version 1.0.12
- Including extension plugins in the plugins parameter caused the module to fail due to a depedancy on the extension to already be installed prior to ckan started.
- This patch incorperates the plugin into the extension so the extension plugins no longer need to be set via the plugin option. It will require 2 puppet runs in order to bring the extensions online though (there isn't any way around this that I know of).
2015-01-29 Version 1.0.11
- Added ckan user password string to ckan.ini.
- Added puppetforge badge
2015-01-28 Version 1.0.10
- Added an option to enable event tracking for the Google Analystics which pushes events every hour
- Added a convience script for creating admin accounts.
- Cleaned up code
- Added documentation for ckan::config
- Added configuration for backup directory
- Added configuration for ckan database password
2015-01-14 Version 1.0.9
- The ckanapi can now be installed (optional)
- A helper script for calling ckanapi command line tool
2015-01-08 Version 1.0.8
- Cleaned up the code based on puppet-lint (via puppetlinter.com)
- Enabled github hook for puppetlinter so future commits are checked and reported
2015-01-07 Version 1.0.7
- Fixed a recent security exploit that has effected CKAN sites globally
- Set the security settings to restrict anonymous users from creating groups and datasets
- Set the default backend for spatial search to solr in the spatial search extension
- Changed backups from weekly to daily
2014-11-12 Version 1.0.6
- CKAN Developers have added a new submodule for managing CKAN extensions.
- Added ckan::ext submodule
- Added Google Analytics extension
- Added Hierarchy extesion
- Added New Zealand Landcare extension
- Added Spatial extension
- Updated to using metadata.json
2014-08-13 Version 1.0.5
- A CKAN Developer has cleaned up the module and prepared for ckan extensions.
- Removed apache module dependency
- Removed module stage complexity with anchor pattern
- Removed hard coded security keys from production.ini.erb
- Added security keys to module parameters
2014-07-23 Version 1.0.4
- Removed the reset_apt module as vagrant can handle updating puppet with a recomended script
- Updated to the latest apache module which has the necessary changes integrated
- Changed default value of the apache headers variable
2014-06-09 Version 1.0.3
- Added dependancy for Debian/Ubuntu based systems only
- Updated readme with new installation parameters
- Added Server admin's email specified
- Added recaptcha support
- Added max_resource_size parameter
- Added data pusher formats
- Added apache head configuration (in order to control search engine crawlers) and is optional
- Added the postgres password as a parameter
- Added postgres hba configuration to pass in as a parameter
2014-06-08 Version 1.0.2
- Fixed a bug if the license was left off, caused errors in datastore
- Added support for CKAN 2.2 package
2014-01-15 Version 1.0.1
- Added a parameter to disable the apt reset
- Removed puppetlabs-apt and apt::ppa which was causing dependency loops if a class outside of ckan required apt::ppa
- Removed ppa for nodejs & ubuntugis
- Added puppetlabs-nodejs class
- Added dependency for puppetlabs-nodejs
Version 1.0.0
- Initial Release.
Dependencies
- puppetlabs/apt (>= 7.0.0 < 8.0.0)
- puppetlabs/concat (>= 6.0.0 < 7.0.0)
- puppetlabs/inifile (>= 4.0.0 < 5.0.0)
- puppet/nodejs (>= 8.0.0 < 9.0.0)
- puppetlabs/postgresql (>= 6.0.0 < 8.0.0)
- puppetlabs/stdlib (>= 6.0.0 < 7.0.0)
- puppetlabs/vcsrepo (>= 3.0.0 < 4.0.0)
- puppet/systemd (>= 3.0.0 < 4.0.0)
- landcareresearch/check_run (>= 6.0.0 < 7.0.0)
- landcareresearch/postgis (>= 6.0.0 < 7.0.0)
- landcareresearch/solr (>= 6.0.0 < 7.0.0)
- puppet/archive (>= 4.4.0 < 7.0.0)
- puppet/nginx (>= 1.0.0 < 2.0.0)
- puppetlabs/apache (>= 5.0.0 < 6.0.0)
GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.