governmentbg/ckan-install

Name: ckan-install

Owner: State e-Government Agency, Republic of Bulgaria

Description: A (semi)automated way to install CKAN

Created: 2015-03-18 13:26:55.0

Updated: 2016-12-04 20:23:10.0

Pushed: 2016-12-04 22:02:57.0

Homepage:

Size: 48

Language: Shell

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

This will setup CKAN 2.3 with:

• file storage enabled
• datastore extension
• datapusher extensions
• a custom theme extention

Currently, the provided setup script is for debian machines only. Tested on Debian 7 (Wheezy).

Usage

1. Clone this repository in the OS temporary folder (usually /tmp). That guarantees all users can read it.
2. Download git submodules: git submodule update --init
3. Setup config. Start with template: cp config.sh.sample config.sh and modify the config.sh to your needs. Whatever password you define in the config for postgres users, make sure you type the same in the installation
4. Guarantee ability to execute scripts: chmod -R 755 ./debian;chmod -R 755 ./bash-utilities/
5. Run install as root: bash debian/init.sh. Keep an eye on the script. It prompts for user input at several times.

After install you might want to:

1. Add additional server aliases at /etc/apache2/sites-available/$CKAN_INSTANCE_NAME
2. Disable user registrations by running bash disable_user_registrations.sh
3. Create users by creating a file and a single user per line in the format: Firstname Lastname;email.address@example.com and running bash batch_user_create.sh your/user/file.txt

Further notes

This project is developed following CKAN install guides. If something's missing in the guide, then the project might be missing the same thing.

If using CKAN 2.2 or lower consider upgrading to CKAN 2.3 or later, because of resource_proxy:

As resource views are rendered on the browser, if the file they are accessing is located in a different domain than the one CKAN is hosted, the browser will block access to it because of the same-origin policy. For instance, files hosted on www.example.com won?t be able to be accessed from the browser if CKAN is hosted on data.catalog.com.

To allow view plugins access to external files you need to activate the resource_proxy plugin on your configuration file:

.resource_proxy.max_file_size

ref:

• http://docs.ckan.org/en/latest/maintaining/data-viewer.html?highlight=recline_view#resource-proxy
• http://docs.ckan.org/en/latest/maintaining/data-viewer.html?highlight=recline_view#migrating-from-previous-ckan-versions