====== DokuWiki Data Refresh ======

Since we have already upgraded DokuWiki and configured it (see below), we can just do a data refresh by grabbing the up-to-date tar.gz of the dokuwiki data directory on to the new server.

On penguin:
<code>
cd /path/to/dokuwiki
tar -sphcvzf ~/dokuwiki-data-penguin.tar.gz ./data
</code>

On lupin:
<code>
scp www.open-ils.org:~/dokuwiki-data-penguin.tar.gz .
tar xvfz  dokuwiki-penguin.tar.gz
rm -rf /root/dokuwiki-xxxx-xx-xx/data
cd /root/dokuwiki-xxxx-xx-xx
mv ~/data .
chown -R www-data.www-data data
</code>

The cache will need to be updated.

<code>
touch /var/www/open-ils.org/dokuwiki/conf/local.php
</code>

====== DokuWiki Migration ======

How to move DokuWiki from one Server to another? - http://www.dokuwiki.org/faq:servermove

The simplest way to do this is to just copy the whole DokuWiki directory to the new server. Note: Upgrade after transferring the data.

On penguin:
<code>
tar -sphcvzf ~/dokuwiki-penguin.tar.gz ./dokuwiki
</code>

On lupin:
<code>
scp www.open-ils.org:~/dokuwiki-penguin.tar.gz .
tar xvfz  dokuwiki-penguin.tar.gz
mv dokuwiki-penguin /root/dokuwiki-xxxx-xx-xx
cd /var/www/open-ils.org/
rm dokuwiki
ln -s /root/dokuwiki-xxxx-xx-xx dokuwiki
</code>

  * The cache might need to be updated.

<code>
touch /var/www/open-ils.org/dokuwiki/conf/local.php
</code>

  * Your .htaccess might need to be tweaked, especially when using URL rewriting

Remove the line which references /usr/share/dokuwiki since it is no longer required.

  * Change css.menu to purecssmenu.css and take out the line that includes javascript.php in the following dokuwiki template.

/var/www/open-ils.org/dokuwiki/lib/tpl/evergreen/main.php

  * Modify layout.css to use the modified subhead class for the new menu delete all subhead entries and use the one used in /css/style.css.

  * Set the correct ownership for the files.

<code>
chown -R www-data.www-data wordpress
</code>

  * Setup maintenance but did not enable the cronjob - http://www.dokuwiki.org/tips:maintenance

===== Upgrade =====

Upgraded to 2010-11-07a “Anteater” [ http://www.splitbrain.org/_media/projects/dokuwiki/dokuwiki-2010-11-07a.tgz ] using these instructions: http://www.dokuwiki.org/install:upgrade

  - Remove install.php : rm /path/to/wiki/install.php
  - Enable acl, disable openregister etc in conf/dokuwiki.conf compare with current dokuwiki.conf there were quite a few missing in the updated configuration file.
  - Installed following plugins for DokuWiki: adminhomepage, confmanager, contactmodern (installed manually), doodle2, fckglite (installed manually), orphanswanted, popularity, pirate (for talk like a pirate day), searchstats and upgrade. We might want to conside piwik (instead of using Google analytics then again we could just add the piwik code into the dokuwiki template) and if we want to make it an all-dokuwiki site use phpwikify or setting phpok it will be a security risk which will need to be discussed)
  - Modify fckglite to remove toolbar options (tbd) [ http://www.mturner.org/fckgLite/doku.php?id=faq&b_disp=1 ]
  - Setup contact form (not sure how useful it will be) another plugin to look at would be bureaucracy. [ http://lupin.georgialibraries.org/dokuwiki/doku.php?id=contact ]

==== reCaptcha ====
Will need to set this up for open-ils.org if we decided to use reCaptcha on production.

**NOTE: The information below is temporary and should not be public if we set it up for production.**

https://www.google.com/recaptcha/admin/site?siteid=314804684

lupin.georgialibraries.org
Domain Name:	lupin.georgialibraries.org
reCAPTCHA will only work on this domain and subdomains. If you have more than one domain (or a staging server), you can create a new set of keys.

Public Key:	6LfMicMSAAAAAIEAtrpJpbqlpfPNMuXWF0FBn9Rk
Use this in the JavaScript code that is served to your users

Private Key:	6LfMicMSAAAAAP6y3fmTZ_aScEvUdkZ4MvPZLEHN
Use this when communicating between your server and our server. Be sure to keep it a secret.

Resources:	
reCAPTCHA plugins and libraries
reCAPTCHA API Documentation

Now what? If you just signed up for a set of keys, you now need to install reCAPTCHA on your site. This is done in two parts. First, you need to add some HTML that displays the reCAPTCHA widget. Second, you need to configure your form to contact our servers to verify reCAPTCHA solutions. Here are specific instructions for: PHP, WordPress, and MediaWiki. For other environments, visit our resources page.