-
Notifications
You must be signed in to change notification settings - Fork 1
How to Install CKAN 2.0 on CentOS 6.3
After rebooting, you can optionally add the ntp package for time syncronization.
yum install ntp ntpdate -s pool.ntp.org chkconfig ntpd on service ntpd start
yum install centos-release-cr
yum update shutdown -r now
rpm -Uvh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-7.noarch.rpm
yum install xml-commons git subversion mercurial postgresql-server postgresql-devel \ postgresql python-devel libxslt libxslt-devel libxml2 libxml2-devel python-virtualenv \ gcc gcc-c++ make java-1.6.0-openjdk-devel java-1.6.0-openjdk tomcat6 xalan-j2 unzip \ policycoreutils-python mod_wsgi
chkconfig postgresql on
service postgresql initdb
Edit /var/lib/pgsql/data/pg_hba.conf so it will accept passwords for login while still allowing the local postgres user to manage via ident login. The relevant changes to pg_hba.conf are as follows:
local all postgres ident local all all md5 # IPv4 local connections: host all all 127.0.0.1/32 md5 # IPv6 local connections: host all all ::1/128 md5
service postgresql start
Become the postgres user.
su - postgres
Create a PostgreSQL database user named ckanuser with a password of pass.
$ createuser -S -D -R -P ckanuser
Create a PostgreSQL database named ckantest with ckanuser as the owner.
$ createdb -O ckanuser ckantest
Exit the postgres user environment.
$ exit
**Note: In the following instructions, replace [DNS] with the actual DNS name of your machine, ex: demo.ckan.net
The ckan user is created with a shell of /sbin/nologin and a home directory of /usr/local/[DNS] to mirror what is shown in the CKAN Deployment documentation.
useradd -m -s /sbin/nologin -d /usr/local/[DNS] -c "CKAN User" ckan
Open the newly created directory up for read access so that the content will eventually be able to be served out via httpd.
chmod 755 /usr/local/[DNS]
Modify the defaults and the current file context of the newly created directory such that it is able to be served out via httpd.
semanage fcontext --add --ftype -- --type httpd_sys_content_t "/usr/local/[DNS](/.*)?" semanage fcontext --add --ftype -d --type httpd_sys_content_t "/usr/local/[DNS](/.*)?" restorecon -vR /usr/local/[DNS]
Become the ckan user.
su -s /bin/bash - ckan
Install an isolated Python environment, called pyenv, to host CKAN from.
$ virtualenv pyenv
Activate the newly installed Python environment.
$ . pyenv/bin/activate
Download and install version 2.0 of CKAN.
(pyenv)$ pip install --ignore-installed -e git+https://github.com/okfn/ckan.git@ckan-2.0#egg=ckan
Download and install the necessary Python modules to run CKAN into the isolated Python environment.
(pyenv)$ pip install --ignore-installed -r pyenv/src/ckan/pip-requirements.txt
Deactivate and then activate the isolated Python environment to start using the added modules.
(pyenv)$ deactivate $ . pyenv/bin/activate
Change to the pyenv/src/ckan directory and create an initial configuration file.
(pyenv)$ cd pyenv/src/ckan (pyenv)$ paster make-config ckan development.ini
Edit the newly created development.ini file, changing the following lines as indicated.
host = [DNS] sqlalchemy.url = postgresql://ckanuser:pass@localhost/ckantest ckan.site_url = [DNS] ckan.site_id = [DNS] ckan.plugins = stats synchronous_search solr_url = http://127.0.0.1:8080/solr/ckan-schema-2.0
Exit from running as the ckan user.
$ exit
CKAN can not use the latest version of Apache SOLR and requires version 1.4.1.
curl http://archive.apache.org/dist/lucene/solr/1.4.1/apache-solr-1.4.1.tgz | tar xzf -
Create directories to hold multiple SOLR cores.
mkdir -p /usr/share/solr/core0 /usr/share/solr/core1 /var/lib/solr/data/core0 \ /var/lib/solr/data/core1 /etc/solr/core0 /etc/solr/core1
Copy the Apache SOLR war to the desired location.
cp apache-solr-1.4.1/dist/apache-solr-1.4.1.war /usr/share/solr
Copy the example Apache SOLR configuration to the core0 directory.
cp -r apache-solr-1.4.1/example/solr/conf /etc/solr/core0
Edit the configuration file, /etc/solr/core0/conf/solrconfig.xml, as follows:
<dataDir>${dataDir}</datadir>
Copy the core0 configuration to core1.
cp -r /etc/solr/core0/conf /etc/solr/core1
Create a symbolic link between the configurations in /etc and /usr.
ln -s /etc/solr/core0/conf /usr/share/solr/core0/conf ln -s /etc/solr/core1/conf /usr/share/solr/core1/conf
Remove the provided schema from the two configured cores and link the schema files in the CKAN source.
rm -f /etc/solr/core0/conf/schema.xml ln -s /usr/local/[DNS]/pyenv/src/ckan/ckan/config/solr/schema-2.0.xml /etc/solr/core0/conf/schema.xml rm -f /etc/solr/core1/conf/schema.xml ln -s /usr/local/[DNS]/pyenv/src/ckan/ckan/config/solr/schema-1.4.xml /etc/solr/core1/conf/schema.xml
Create a new file, called /etc/tomcat6/Catalina/localhost/solr.xml, with the following contents:
<Context docBase="/usr/share/solr/apache-solr-1.4.1.war" debug="0" privileged="true" allowLinking="true" crossContext="true"> <Environment name="solr/home" type="java.lang.String" value="/usr/share/solr" override="true" /> </context>
Create a new file, called /usr/share/solr/solr.xml, with the following contents:
<solr persistent="true" sharedLib="lib">
<cores adminPath="/admin/cores">
<core name="ckan-schema-2.0" instanceDir="core0">
<property name="dataDir" value="/var/lib/solr/data/core0" />
</core>
<core name="ckan-schema-1.4" instanceDir="core1">
<property name="dataDir" value="/var/lib/solr/data/core1" />
</core>
</cores>
</solr>
Make tomcat the owner of the SOLR directories.
chown -R tomcat:tomcat /usr/share/solr /var/lib/solr
Configure Tomcat 6 to start on system boot.
chkconfig tomcat6 on
Start Tomcat 6.
service tomcat6 start
Now that Apache SOLR is being served via Tomcat 6, the final steps of the CKAN configuration can now be performed
Switch back to running as the ckan user, activate the isolated Python environment, and change to the CKAN source directory.
su -s /bin/bash - ckan $ . pyenv/bin/activate (pyenv)$ cd pyenv/src/ckan
Initialize the CKAN database.
(pyenv)$ paster --plugin=ckan db init
Add a user named admin to the CKAN database.
(pyenv)$ paster --plugin=ckan user add admin --config=development.ini
Grant the admin user sysadmin rights.
(pyenv)$ paster --plugin=ckan sysadmin add admin --config=development.ini
Edit /usr/local/[DNS]/pyenv/src/ckan/development.ini and change its log location as follows:
args = ("/var/log/ckan/[DNS]/ckan.log", "a", 20000000, 9)
Create a Python script called /usr/local/[DNS]/pyenv/bin/[DNS].py to run via mod_wsgi with the following contents:
import os
instance_dir = '/usr/local/[DNS]'
config_file = '/usr/local/[DNS]/pyenv/src/ckan/development.ini'
pyenv_bin_dir = os.path.join(instance_dir, 'pyenv', 'bin')
activate_this = os.path.join(pyenv_bin_dir, 'activate_this.py')
execfile(activate_this, dict(__file__=activate_this))
from paste.deploy import loadapp
config_filepath = os.path.join(instance_dir, config_file)
from paste.script.util.logging_config import fileConfig
fileConfig(config_filepath)
application = loadapp('config:%s' % config_filepath)
Exit running as the ckan user.
$ exit
Make the following directories and modify the permissions such that the apache user can write to them.
mkdir -p /usr/local/[DNS]/pyenv/src/ckan/data /usr/local/[DNS]/pyenv/src/ckan/sstore /var/log/ckan/[DNS] chmod g+w /usr/local/[DNS]/pyenv/src/ckan/data /usr/local/[DNS]/pyenv/src/ckan/sstore /var/log/ckan/[DNS] chown apache:apache /usr/local/[DNS]/pyenv/src/ckan/data /usr/local/[DNS]/pyenv/src/ckan/sstore /var/log/ckan/[DNS]
Edit the file /etc/httpd/conf.d/wsgi.conf and add the following contents:
<VirtualHost *:80> ServerName [DNS] ServerAlias [DNS] WSGIScriptAlias / /usr/local/[DNS]/pyenv/bin/[DNS].py WSGIPassAuthorization On ErrorLog /var/log/httpd/[DNS].log CustomLog /var/log/httpd/[DNS].custom.log combined </virtualhost>
setsebool -P httpd_can_network_connect 1
chkconfig httpd on
service httpd start
Edit the file /etc/sysconfig/iptables by inserting the following line near the middle of the file:
-A INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT
service iptables restart
Start your web browser and head to [DNS] and you should see CKAN running. Login as the username admin as created previously.