SWiK-Source is the source code of the [[SWiK|swik.net]] core engine. It is licensed for distribution under the [[License:GPL|GNU General Public License v2]].

SWiK-Source is meant for people who are curious about the code that powers SWiK, for people who want to try making their own SWiK for their internal use or for some new web site, as well as for use with [[SourceLabs]]' internal and partnering projects.

SourceLabs has released SWiK-Source as a source code release rather than a packaged release: it's a complicated system built with a lot of assumptions for custom production servers rather than arbitrary or generic systems.

h3{margin-top:3em;}. Installation

Setup and Deployment of SWiK Source is a {{Installation|3 step process}}.

# {{Installing Dependencies}}

# {{Setup and Deployment}}

# {{Backend Deployment}}docs!

SWiK-Source is the source code of the [[SWiK|swik.net]] core engine. It is licensed for distribution under the [[License:GPL|GNU General Public License v2]].

SWiK-Source is meant for people who are curious about the code that powers SWiK, for people who want to try making their own SWiK for their internal use or for some new web site, as well as for use with [[SourceLabs]]' internal and partnering projects.

SourceLabs has released SWiK-Source as a source code release rather than a packaged release: it's a complicated system built with a lot of assumptions for custom production servers rather than arbitrary or generic systems.

h3{margin-top:3em;}. Installation

Setup and Deployment of SWiK Source is a {{Installation|3 step process}}.

# {{Installing Dependencies}}

# {{Setup and Deployment}}

# {{Backend Deployment}}docs! Deployment}}

Notes:

* {{Localhost Install Notes|Installing to run on 'localhost' rather than a dedicated server}}

p(notice). These documents are collaborative: if you run into trouble or see something wrong, fix the docs!

p(notice). After you have {{Installing Dependencies|installed dependencies}}, {{Setup and Deployment|setup and configured}} the server, you are now ready to setup and deploy the backend.

There are various long running services that [[SWiK Source]] runs on the backend. These include: RSS aggregation, and various page and tag statistics computations.

---

h2. Before You Start

The backend is mostly Java based and requires Java version 1.5, so make sure that you have Java 1.5 installed - you can obtain this from Sun, instructions are below, or "skip to the 2nd step":#deploybackend if you have java already.

Again, in these instructions the root directory of SWiK Source where you expanded the source files will be referred to as SWIK_HOME.

h3{margin-top:3em;}. Step 1: Install Java 1.5

You must have JDK 1.5.x installed on your machine. These instructions detail how to download and install the Java 1.5 JDK. You should install the latest minor release.

Download the x86-64 version of the "JDK":http://java.sun.com/j2se/1.5.0/download.jsp. Pick the proper Java 1.5 JDK for your machine. These instructions assume you downloaded the AMD64 version, adjust as necessary for your own environment.

Run the self-extracting .bin file:

<pre><code>

chmod a+x jdk-1_5_0_05-linux-amd64-rpm.bin*

./jdk-1_5_0_05-linux-amd64-rpm.bin*

</code></pre>

As root, install the RPM that emerges:

<pre><code>

rpm -iv jdk-1_5_0_<version>-linux-i586.rpm

</code></pre>(notice). </code></pre>dddddddddddddddddddddddddddddddddddddd

p(notice). These instruction assume that the new Java is on your path. At this point you should add the new version of Java to your path.

* Verify that you are running 1.5, the required version of Java.

<pre><code>

java -version

</code></pre>

* You should see something like:

<pre><code>

java version "1.5.0_05"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05)

Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_05-b05, mixed mode)

</code></pre>

<h3 style='margin-top:3em;' id='deploybackend'>Step 2: Deploy the Backend</h3>

Now you need to deploy your backend. The script assumes that Java 1.5 is on your path when you execute the script. If this is not true you'll need to modify the script to pick up the proper version of Java.

<pre><code>

cd SWIK_HOME/setup

bash -x ./backend_setup.sh config

</code></pre>

This should start the backend. You can verify this by looking in the /opt/swik/backend/logs directory and verify that there are three sets of logs, feedsucker, strength and zeitgrinder. There should be both a status and error log for each.

p(notice). After you have {{Installing Dependencies|installed dependencies}}, {{Setup and Deployment|setup and configured}} the server, you are now ready to setup and deploy the backend.

There are various long running services that [[SWiK Source]] runs on the backend. These include: RSS aggregation, and various page and tag statistics computations.

---

h2. Before You Start

The backend is mostly Java based and requires Java version 1.5, so make sure that you have Java 1.5 installed - you can obtain this from Sun, instructions are below, or "skip to the 2nd step":#deploybackend if you have java already.

Again, in these instructions the root directory of SWiK Source where you expanded the source files will be referred to as SWIK_HOME.

h3{margin-top:3em;}. Step 1: Install Java 1.5

You must have JDK 1.5.x installed on your machine. These instructions detail how to download and install the Java 1.5 JDK. You should install the latest minor release.

Download the x86-64 version of the "JDK":http://java.sun.com/j2se/1.5.0/download.jsp. Pick the proper Java 1.5 JDK for your machine. These instructions assume you downloaded the AMD64 version, adjust as necessary for your own environment.

Run the self-extracting .bin file:

<pre><code>

chmod a+x jdk-1_5_0_05-linux-amd64-rpm.bin*

./jdk-1_5_0_05-linux-amd64-rpm.bin*

</code></pre>

As root, install the RPM that emerges:

<pre><code>

rpm -iv jdk-1_5_0_<version>-linux-i586.rpm

</code></pre>dddddddddddddddddddddddddddddddddddddd </code></pre>

p(notice). These instruction assume that the new Java is on your path. At this point you should add the new version of Java to your path.

* Verify that you are running 1.5, the required version of Java.

<pre><code>

java -version

</code></pre>

* You should see something like:

<pre><code>

java version "1.5.0_05"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05)

Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_05-b05, mixed mode)

</code></pre>

<h3 style='margin-top:3em;' id='deploybackend'>Step 2: Deploy the Backend</h3>

Now you need to deploy your backend. The script assumes that Java 1.5 is on your path when you execute the script. If this is not true you'll need to modify the script to pick up the proper version of Java.

<pre><code>

cd SWIK_HOME/setup

bash -x ./backend_setup.sh config

</code></pre>

This should start the backend. You can verify this by looking in the /opt/swik/backend/logs directory and verify that there are three sets of logs, feedsucker, strength and zeitgrinder. There should be both a status and error log for each.

p(notice). After you have {{Installing Dependencies|installed dependencies}}, {{Setup and Deployment|setup and configured}} the server, you are now ready to setup and deploy the backend.

There are various long running services that [[SWiK Source]] runs on the backend. These include: RSS aggregation, and various page and tag statistics computations.

---

h2. Before You Start

The backend is mostly Java based and requires Java version 1.5, so make sure that you have Java 1.5 installed - you can obtain this from Sun, instructions are below, or "skip to the 2nd step":#deploybackend if you have java already.

Again, in these instructions the root directory of SWiK Source where you expanded the source files will be referred to as SWIK_HOME.

h3{margin-top:3em;}. Step 1: Install Java 1.5

You must have JDK 1.5.x installed on your machine. These instructions detail how to download and install the Java 1.5 JDK. You should install the latest minor release.

Download the x86-64 version of the "JDK":http://java.sun.com/j2se/1.5.0/download.jsp. Pick the proper Java 1.5 JDK for your machine. These instructions assume you downloaded the AMD64 version, adjust as necessary for your own environment.

Run the self-extracting .bin file:

<pre><code>

chmod a+x jdk-1_5_0_05-linux-amd64-rpm.bin*

./jdk-1_5_0_05-linux-amd64-rpm.bin*

</code></pre>

As root, install the RPM that emerges:

<pre><code>

rpm -iv jdk-1_5_0_<version>-linux-i586.rpm

</code></pre>

p(notice). These instruction assume that the new Java is on your path. At this point you should add the new version of Java to your path.

* Verify that you are running 1.5, the required version of Java.

<pre><code>

java -version

</code></pre>

* You should see something like:

<pre><code>

java version "1.5.0_05"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05)

Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_05-b05, mixed mode)

</code></pre>

<h3 style='margin-top:3em;' id='deploybackend'>Step 2: Deploy the Backend</h3>

Now you need to deploy your backend. The script assumes that Java 1.5 is on your path when you execute the script. If this is not true you'll need to modify the script to pick up the proper version of Java.

<pre><code>

cd SWIK_HOME/setup

bash -x ./backend_setup.sh config

</code></pre>

This should start the backend. You can verify this by looking in the /opt/swik/backend/logs directory and verify that there are three sets of logs, feedsucker, strength and zeitgrinder. There should be both a status and error log for each.

SWiK-Source is the source code of the [[SWiK|swik.net]] core engine. It is licensed for distribution under the [[License:GPL|GNU General Public License v2]].

SWiK-Source is meant for people who are curious about the code that powers SWiK, for people who want to try making their own SWiK for their internal use or for some new web site, as well as for use with [[SourceLabs]]' internal and partnering projects.

SourceLabs has released SWiK-Source as a source code release rather than a packaged release: it's a complicated system built with a lot of assumptions for custom production servers rather than arbitrary or generic systems.

h3{margin-top:3em;}. Installation

Setup and Deployment of SWiK Source is a {{Installation|3 step process}}.

# {{Installing Dependencies}}

# {{Setup and Deployment}}

# {{Backend Deployment}}

Notes:

* {{Localhost Install Notes|Installing to run on 'localhost' rather than a dedicated server}}

p(notice). These documents are collaborative: if you run into trouble or see something wrong, fix the docs!

h3{margin-top:3em;}. Installation

Setup and Deployment of SWiK Source is a {{Installation|3 step process}}.

# {{Installing Dependencies}}

# {{Setup and Deployment}}

# {{Backend Deployment}}

Notes:

* {{Localhost Install Notes|Installing to run on 'localhost' rather than a dedicated server}}

p(notice). These documents are collaborative: if you run into trouble or see something wrong, fix the docs!

SWiK-Source is the source code of the [[SWiK|swik.net]] core engine. It is licensed for distribution under the [[License:GPL|GNU General Public License v2]].

SWiK-Source is meant for people who are curious about the code that powers SWiK, for people who want to try making their own SWiK for their internal use or for some new web site, as well as for use with [[SourceLabs]]' internal and partnering projects.

SourceLabs has released SWiK-Source as a source code release rather it's a complicated system built with a lot of assumptions for custom production servers rather than arbitrary or generic systems.

h3{margin-top:3em;}. Installation

Setup and Deployment of SWiK Source is a {{Installation|3 step process}}.

# {{Installing Dependencies}}

# {{Setup and Deployment}}

# {{Backend Deployment}}

Notes:

* {{Localhost Install Notes|Installing to run on 'localhost' rather than a dedicated server}}

p(notice). These documents are collaborative: if you run into trouble or see something wrong, fix the docs!

SWiK-Source is the source code of the [[SWiK|swik.net]] core engine. It is licensed for distribution under the [[License:GPL|GNU General Public License v2]].

SWiK-Source is meant for people who are curious about the code that powers SWiK, for people who want to try making their own SWiK for their internal use or for some new web site, as well as for use with [[SourceLabs]]' internal and partnering projects.

SourceLabs has released SWiK-Source as a source code release rather than a packaged release: it's a complicated system built with a lot of assumptions for custom production servers rather than arbitrary or generic systems.

h3{margin-top:3em;}. Installation

Setup and Deployment of SWiK Source is a {{Installation|3 step process}}.

# {{Installing Dependencies}}

# {{Setup and Deployment}}

# {{Backend Deployment}}

Notes:

* {{Localhost Install Notes|Installing to run on 'localhost' rather than a dedicated server}}

p(notice). These documents are collaborative: if you run into trouble or see something wrong, fix the docs!

SWiK-Source is the source code of the [[SWiK|swik.net]] core engine. It is licensed for distribution under the [[License:GPL|GNU General Public License v2]].

SWiK-Source is meant for people who are curious about the code that powers SWiK, for people who want to try making their own SWiK for their internal use or for some new web site, as well as for use with [[SourceLabs]]' internal and partnering projects.

SourceLabs has released SWiK-Source as a source code release rather than a packaged release: it's a complicated system built with a lot of assumptions for custom production servers rather than arbitrary or generic systems.

h3{margin-top:3em;}. Installation

Setup and Deployment of SWiK Source is a {{Installation|3 step process}}.

# {{Installing Dependencies}}

# {{Setup and Deployment}}

# {{Backend Deployment}}

Notes:

* {{Localhost Install Notes|Installing to run on 'localhost' rather than a dedicated server}}

p(notice). These documents are collaborative: if you run into trouble or see something wrong, fix the docs!

SWiK-Source is the source code of the [[SWiK|swik.net]] core engine. It is licensed for distribution under the [[License:GPL|GNU General Public License v2]].

SWiK-Source is meant for people who are curious about the code that powers SWiK, for people who want to try making their own SWiK for their internal use or for some new web site, as well as for use with [[SourceLabs]]' internal and partnering projects.

SourceLabs has released SWiK-Source as a source code release rather than a packaged release: it's a complicated system built with a lot of assumptions for custom production servers rather than arbitrary or generic systems.

h3{margin-top:3em;}. Installation

Setup and Deployment of SWiK Source is a {{Installation|3 step process}}.

# {{Installing Dependencies}}

# {{Setup and Deployment}}

# {{Backend Deployment}}

Notes:

* {{Localhost Install Notes|Installing to run on 'localhost' rather than a dedicated server}}

p(notice). These documents are collaborative: if you run into trouble or see something wrong, fix the docs!

p(notice). After you have {{Installing Dependencies|installed dependencies}}, {{Setup and Deployment|setup and configured}} the server, you are now ready to setup and deploy the backend.

There are various long running services that [[SWiK Source]] runs on the backend. These include: RSS aggregation, and various page and tag statistics computations.

---

h2. Before You Start

The backend is mostly Java based and requires Java version 1.5, so make sure that you have Java 1.5 installed - you can obtain this from Sun, instructions are below, or "skip to the 2nd step":#deploybackend if you have java already.

Again, in these instructions the root directory of SWiK Source where you expanded the source files will be referred to as SWIK_HOME.

h3{margin-top:3em;}. Step 1: Install Java 1.5

You must have JDK 1.5.x installed on your machine. These instructions detail how to download and install the Java 1.5 JDK. You should install the latest minor release.

Download the x86-64 version of the "JDK":http://java.sun.com/j2se/1.5.0/download.jsp. Pick the proper Java 1.5 JDK for your machine. These instructions assume you downloaded the AMD64 version, adjust as necessary for your own environment.

Run the self-extracting .bin file:

<pre><code>

chmod a+x jdk-1_5_0_05-linux-amd64-rpm.bin*

./jdk-1_5_0_05-linux-amd64-rpm.bin*

</code></pre>

As root, install the RPM that emerges:

<pre><code>

rpm -iv jdk-1_5_0_<version>-linux-i586.rpm

</code></pre>

p(notice). These instruction assume that the new Java is on your path. At this point you should add the new version of Java to your path.

* Verify that you are running 1.5, the required version of Java.

<pre><code>

java -version

</code></pre>

* You should see something like:

<pre><code>

java version "1.5.0_05"

Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_05-b05)

Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_05-b05, mixed mode)

</code></pre>

<h3 style='margin-top:3em;' id='deploybackend'>Step 2: Deploy the Backend</h3>

Now you need to deploy your backend. The script assumes that Java 1.5 is on your path when you execute the script. If this is not true you'll need to modify the script to pick up the proper version of Java.

<pre><code>

cd SWIK_HOME/setup

bash -x ./backend_setup.sh config

</code></pre>

This should start the backend. You can verify this by looking in the /opt/swik/backend/logs directory and verify that there are three sets of logs, feedsucker, strength and zeitgrinder. There should be both a status and error log for each.

Thing that often break in [[SWiK-Source]], and why they break. The best way to diagnose problems is to check in the /logs directory. app.errors.log is a good place to look for application errors that occur on page load, app.ajax-errors.log is a good place to look for errors that occur through interactivity with [[ajax]] features.

h2. SWiK fails to respond at all or and returns a white page.

SWiK assumes a dedicated domain, such as swik.net, or no domain, for use in local host, see {{localhost install notes}}. The domain _must not have a subdomain_. Requests to SWiK are sent to apache through the virtual host setup, and then apache passes the request to swik.php, along with the raw query string. SWiK parses the query string and goes through each major page type, using an inverted control scheme to ask if a page wants to service the request.

This can go wrong because:

* the requests aren't being sent to swik: a virtual host setting is wrong, or a DNS issue

* an error has been triggered and swik source is configured to hide errors.

* an invalid swik domain has been used.

h2. User and license pages fail to work properly

SWiK-Source does not encode the ':' entity in urls such as [[User:alex]]. On [[Unix]] in [[Apache|Apache 2.0]], this is allowed, on Windows OR in Apache 1.0 this is not.

To fix this issue:

* switch to Apache 2.0

* do not host a swik-source wiki on windows

* fix the bug in apache on windows.

h2. Save a wiki page -> no text appears.

This occurs because SWiK execs a ruby textile script to generate the description cache, and it may have difficulty .

This can be because:

* tmp file privileges are improperly set

* ruby is not installed or the path to it is incorrect

check both these things.

h2. RSS feeds do not syndicate properly

RSS feeds are syndicated using a temporary file, and then parsed with [[MagpieRSS]].

If there is an issue with this, it can be because:

* tmp file privileges are improperly set

* the path to swik-configure is improperly set

h2. Icon upload fails

Icon uploads use a two stage system. First the icon is persisted into the database; on the next request the icon is cached into a web directory. This is to ensure a single store for a multi-web-server environment, and cache icons for fast access.

If there is a problem with icon upload, it can be because:

* the swikIcons directory is not created or has bad privs for the server to write to.

* a [[libpng]] or [[libjpg]] library failure.

[[SWiK Source]] is built on and integrated with the platform combination of PHP, MySQL, and Apache HTTPd. These applications are not packaged as part of the distribution, however SWiK Source requires these and other 3rd party open source components to run properly.

List of components you must either have or obtain and install before setting up SWiK Source:

# [[PHP]] 5.0 (see "below for specific configure line":#buildphp)

# [[Apache]] 2.0

# [[MySQL]] 4.1

# [[Ruby]]

# [[Java]]

# [[libxml]]

# "libjpg":http://www.ijg.org/files/jpegsrc.v6b.tar.gz

# "libpng":http://heanet.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.6rc5.tar.gz

Install these components yourself, or look down for how to compile these from source.

After you have completed installation of these components, continue to {{Setup and Deployment}}.

<br>

h2. Step by step instructions for downloading and installing components

p(notice). *Note:* These instructions assume you will make a directory called /usr/local/work and

do your downloads and installations from there. If you deviate from this, please be careful to note instructions specific to this install directory.

p(notice). *Note:* Many of these steps involve installing and configuring system level software, as such the steps assume that you are running as root. ("su -", "sudo bash", etc). If you are concerned about running as root, you can run much of the configuration without the privilege but please note steps that will have system level impact and do sudo accordingly.

Finally, all the steps assume you are setting your wiki up on a clean machine. If you have previous installations of components, you'll have to adjust these instructions accordingly to make sure that your installations match the dependencies.

If you are using a package management system (such as yum on CentOS or Fedora) you can just make sure you've got the right packages installed, skipping all the following steps. For a CentOS 4.3 install, we used the following packages:

php-5.0.4-5.centos4

php-pear-5.0.4-5.centos4

php-ldap-5.0.4-5.centos4

php-mysql-5.0.4-5.centos4

php-mbstring-5.0.4-5.centos4

php-xml-5.0.4-5.centos4

php-imap-5.0.4-5.centos4

php-gd-5.0.4-5.centos4

php-xmlrpc-5.0.4-5.centos4

php-devel-5.0.4-5.centos4

httpd-suexec-2.0.52-22.ent.centos4

httpd-2.0.52-22.ent.centos4

httpd-devel-2.0.52-22.ent.centos4

mysqlclient10-3.23.58-4.RHEL4.1

mysql-4.1.20-1.RHEL4.1

mysql-server-4.1.20-1.RHEL4.1

On RedHat based systems, you can verify these are installed using 'rpm -qa | grep [php|httpd|mysql]'

<br>

For installation on Ubuntu, here are the package matches discovered so far:

php-5.0.4-5.centos4 - *php5*

php-pear-5.0.4-5.centos4 - *php-pear*

php-ldap-5.0.4-5.centos4 - *php5-ldap*

php-mysql-5.0.4-5.centos4 - *php5-mysql*

php-mbstring-5.0.4-5.centos4 - - *libapache2-mod-php5*

php-xml-5.0.4-5.centos4 - *php-xml-parser* (?)

php-imap-5.0.4-5.centos4 - *php5-imap*

php-gd-5.0.4-5.centos4 - *php5-gd*

php-xmlrpc-5.0.4-5.centos4 - *php5-xmlrpc*

php-devel-5.0.4-5.centos4 - *php5-dev* (?)

httpd-suexec-2.0.52-22.ent.centos4 - - *apache2-mpm-perchild* (?)

httpd-2.0.52-22.ent.centos4 - - *apache2* (?)

httpd-devel-2.0.52-22.ent.centos4 - *apache2-utils* (?)

mysqlclient10-3.23.58-4.RHEL4.1 - *mysql-client*

mysql-4.1.20-1.RHEL4.1 - *mysql-common* (?)

mysql-server-4.1.20-1.RHEL4.1 - *mysql-server*

libpng - *libpng12-0*

libjpg - *libjpeg62*

Java - *sun-java5-jdk*

Ruby - *ruby*

<br>

h3. *Step 1: Download*

These are the primary versions which have been fully tested for SWiK Source. It should be fine to use new minor release, but some higher point releases may break.

* httpd-2.0.54.tar.bz2 - A new point release or slightly older release should be fine. There may be issues with 2.2 branch however. "Distribution":http://archive.apache.org/dist/httpd/

* php-5.0.4.tar.bz2 - There may be issues with 5.1. branch, 4.x or early releases will not work at all. "Distribution":http://www.php.net/releases.php

* libxml2-2.6.17.tar.gz - "ftp://ftp.xmlsoft.org/libxml2/libxml2-2.6.17.tar.gz":ftp://ftp.xmlsoft.org/libxml2/libxml2-2.6.17.tar.gz

* mysql-standard-4.1.12 - There may be issues with the 5.0 branch. "Distributions":http://dev.mysql.com/downloads/index.html

<br>

h3. *Step 2: Install MySQL*

Run the installer. The installer puts everything in /usr/local/mysql-blahblah and links to it from /usr/local/mysql. Set a root password!, or not (it's a lot easier to manipulate data when you don't ... sure is a lot more secure when you do).

<br>

h3. *Step 3: Install Apache2*

cd /usr/local/work

tar xfj httpd-2.0.54.tar.bz2

cd httpd-2.0.54

./configure --prefix=/usr/local/apache2 --enable-so --enable-rewrite=shared --with-mpm=prefork --enable-expires=shared

make && make install

p(notice). *Note:* The httpd.conf will be configured later, when setting up and deploying the wiki.

<br>

h3. *Step 4: Build and Install libxml2*

cd /usr/local/work

tar xfz libxml2-2.6.17.tar.gz

cd libxml2-2.6.17

./configure --prefix=/usr/local

make && make install

<br>

h3. *Step 5: Download the Graphics Libraries*

The JPEG and PNG libraries for working with images need to be downloaded.

<pre><code>

cd /usr/local/work

curl -O http://www.ijg.org/files/jpegsrc.v6b.tar.gz

curl -O http://heanet.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.6rc5.tar.gz

gnutar xzf jpegsrc.v6b.tar.gz

gnutar xzf libpng-1.2.6rc5.tar.gz

</code></pre>

<br>

h3. *Step 6: Build and Install the JPEG library*

* Build and install the jpeg-6b library:

<pre><code>

cd jpeg-6b

./configure

make install

make install-lib

ranlib /usr/local/lib/libjpeg.a

cd ..

</code></pre>

<br>

h3. *Step 7: Build and Install the PNG library*

* First copy the correct makefile for your environment (.darwin for osx, .linux for linux, etc).

cd libpng-1.2.6rc5

cp scripts/makefile.your_environment ./Makefile

You need to make a few changes to the Makefile to point at your zlib locations before you build the library.

EDITOR_PROGRAM Makefile

* Find the following lines:

<pre><code>

# Where the zlib library and include files are located

#ZLIBLIB=/usr/local/lib

#ZLIBINC=/usr/local/include

ZLIBLIB=../zlib

ZLIBINC=../zlib

</pre></code>

* Reverse the comments to this:

<pre><code>

# Where the zlib library and include files are located

ZLIBLIB=/usr/local/lib

ZLIBINC=/usr/local/include

#ZLIBLIB=../zlib

#ZLIBINC=../zlib

</pre></code>

* Now build and install the PNG library:

make

make install

ranlib /usr/local/lib/libpng.a

<h3 style='margin-top:3em;' id='buildphp'>Step 8: Build PHP</h3>

<pre><code>

cd /usr/local/work

tar xfj ~/php-5.0.4.tar.bz2

cd php-5.0.4

./configure --prefix=/usr/local/php5

--with-apxs2=/usr/local/apache2/bin/apxs

--with-mysqli=/usr/local/mysql/bin/mysql_config --with-mysql=/usr/local/mysql

--enable-mbstring --enable-mbregex --enable-soap --with-libxml2=/usr/local

--with-zlib=/usr --with-iconv --with-gd --with-jpeg-dir=/usr/local/work/jpeg-6b

make && make install

</pre></code>

p(notice). *Note:* php.ini will be setup later.

---

If you successfully completed these steps, you've now got the platform for [[SWiK Source]] to run. Please continue to the next step: SWiK Source {{Setup and Deployment}}.

[[SWiK Source]] is built on and integrated with the platform combination of PHP, MySQL, and Apache HTTPd. These applications are not packaged as part of the distribution, however SWiK Source requires these and other 3rd party open source components to run properly.

List of components you must either have or obtain and install before setting up SWiK Source:

# [[PHP]] 5.0 (see "below for specific configure line":#buildphp)

# [[Apache]] 2.0

# [[MySQL]] 4.1

# [[Ruby]]

# [[Java]]

# [[libxml]]

# "libjpg":http://www.ijg.org/files/jpegsrc.v6b.tar.gz

# "libpng":http://heanet.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.6rc5.tar.gz

Install these components yourself, or look down for how to compile these from source.

After you have completed installation of these components, continue to {{Setup and Deployment}}.

<br>

h2. Step by step instructions for downloading and installing components

p(notice). *Note:* These instructions assume you will make a directory called /usr/local/work and

do your downloads and installations from there. If you deviate from this, please be careful to note instructions specific to this install directory.

p(notice). *Note:* Many of these steps involve installing and configuring system level software, as such the steps assume that you are running as root. ("su -", "sudo bash", etc). If you are concerned about running as root, you can run much of the configuration without the privilege but please note steps that will have system level impact and do sudo accordingly.

Finally, all the steps assume you are setting your wiki up on a clean machine. If you have previous installations of components, you'll have to adjust these instructions accordingly to make sure that your installations match the dependencies.

If you are using a package management system (such as yum on CentOS or Fedora) you can just make sure you've got the right packages installed, skipping all the following steps. For a CentOS 4.3 install, we used the following packages:

php-5.0.4-5.centos4

php-pear-5.0.4-5.centos4

php-ldap-5.0.4-5.centos4

php-mysql-5.0.4-5.centos4

php-mbstring-5.0.4-5.centos4

php-xml-5.0.4-5.centos4

php-imap-5.0.4-5.centos4

php-gd-5.0.4-5.centos4

php-xmlrpc-5.0.4-5.centos4

php-devel-5.0.4-5.centos4

httpd-suexec-2.0.52-22.ent.centos4

httpd-2.0.52-22.ent.centos4

httpd-devel-2.0.52-22.ent.centos4

mysqlclient10-3.23.58-4.RHEL4.1

mysql-4.1.20-1.RHEL4.1

mysql-server-4.1.20-1.RHEL4.1

On RedHat based systems, you can verify these are installed using 'rpm -qa | grep [php|httpd|mysql]'

<br>

For installation on Ubuntu, here are the package matches discovered so far:

php-5.0.4-5.centos4 - *php5*

php-pear-5.0.4-5.centos4 - *php-pear*

php-ldap-5.0.4-5.centos4 - *php5-ldap*

php-mysql-5.0.4-5.centos4 - *php5-mysql*

php-mbstring-5.0.4-5.centos4 - - *libapache2-mod-php5*

php-xml-5.0.4-5.centos4 - *php-xml-parser* (?)

php-imap-5.0.4-5.centos4 - *php5-imap*

php-gd-5.0.4-5.centos4 - *php5-gd*

php-xmlrpc-5.0.4-5.centos4 - *php5-xmlrpc*

php-devel-5.0.4-5.centos4 - *php5-dev* (?)

httpd-suexec-2.0.52-22.ent.centos4 - - *apache2-mpm-perchild* (?)

httpd-2.0.52-22.ent.centos4 - - *apache2* (?)

httpd-devel-2.0.52-22.ent.centos4 - *apache2-utils* (?)

mysqlclient10-3.23.58-4.RHEL4.1 - *mysql-client*

mysql-4.1.20-1.RHEL4.1 - *mysql-common* (?)

mysql-server-4.1.20-1.RHEL4.1 - *mysql-server*

libpng - *libpng12-0*

libjpg - *libjpeg62*

<br>

h3. *Step 1: Download*

These are the primary versions which have been fully tested for SWiK Source. It should be fine to use new minor release, but some higher point releases may break.

* httpd-2.0.54.tar.bz2 - A new point release or slightly older release should be fine. There may be issues with 2.2 branch however. "Distribution":http://archive.apache.org/dist/httpd/

* php-5.0.4.tar.bz2 - There may be issues with 5.1. branch, 4.x or early releases will not work at all. "Distribution":http://www.php.net/releases.php

* libxml2-2.6.17.tar.gz - "ftp://ftp.xmlsoft.org/libxml2/libxml2-2.6.17.tar.gz":ftp://ftp.xmlsoft.org/libxml2/libxml2-2.6.17.tar.gz

* mysql-standard-4.1.12 - There may be issues with the 5.0 branch. "Distributions":http://dev.mysql.com/downloads/index.html

<br>

h3. *Step 2: Install MySQL*

Run the installer. The installer puts everything in /usr/local/mysql-blahblah and links to it from /usr/local/mysql. Set a root password!, or not (it's a lot easier to manipulate data when you don't ... sure is a lot more secure when you do).

<br>

h3. *Step 3: Install Apache2*

cd /usr/local/work

tar xfj httpd-2.0.54.tar.bz2

cd httpd-2.0.54

./configure --prefix=/usr/local/apache2 --enable-so --enable-rewrite=shared --with-mpm=prefork --enable-expires=shared

make && make install

p(notice). *Note:* The httpd.conf will be configured later, when setting up and deploying the wiki.

<br>

h3. *Step 4: Build and Install libxml2*

cd /usr/local/work

tar xfz libxml2-2.6.17.tar.gz

cd libxml2-2.6.17

./configure --prefix=/usr/local

make && make install

<br>

h3. *Step 5: Download the Graphics Libraries*

The JPEG and PNG libraries for working with images need to be downloaded.

<pre><code>

cd /usr/local/work

curl -O http://www.ijg.org/files/jpegsrc.v6b.tar.gz

curl -O http://heanet.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.6rc5.tar.gz

gnutar xzf jpegsrc.v6b.tar.gz

gnutar xzf libpng-1.2.6rc5.tar.gz

</code></pre>

<br>

h3. *Step 6: Build and Install the JPEG library*

* Build and install the jpeg-6b library:

<pre><code>

cd jpeg-6b

./configure

make install

make install-lib

ranlib /usr/local/lib/libjpeg.a

cd ..

</code></pre>

<br>

h3. *Step 7: Build and Install the PNG library*

* First copy the correct makefile for your environment (.darwin for osx, .linux for linux, etc).

cd libpng-1.2.6rc5

cp scripts/makefile.your_environment ./Makefile

You need to make a few changes to the Makefile to point at your zlib locations before you build the library.

EDITOR_PROGRAM Makefile

* Find the following lines:

<pre><code>

# Where the zlib library and include files are located

#ZLIBLIB=/usr/local/lib

#ZLIBINC=/usr/local/include

ZLIBLIB=../zlib

ZLIBINC=../zlib

</pre></code>

* Reverse the comments to this:

<pre><code>

# Where the zlib library and include files are located

ZLIBLIB=/usr/local/lib

ZLIBINC=/usr/local/include

#ZLIBLIB=../zlib

#ZLIBINC=../zlib

</pre></code>

* Now build and install the PNG library:

make

make install

ranlib /usr/local/lib/libpng.a

<h3 style='margin-top:3em;' id='buildphp'>Step 8: Build PHP</h3>

<pre><code>

cd /usr/local/work

tar xfj ~/php-5.0.4.tar.bz2

cd php-5.0.4

./configure --prefix=/usr/local/php5

--with-apxs2=/usr/local/apache2/bin/apxs

--with-mysqli=/usr/local/mysql/bin/mysql_config --with-mysql=/usr/local/mysql

--enable-mbstring --enable-mbregex --enable-soap --with-libxml2=/usr/local

--with-zlib=/usr --with-iconv --with-gd --with-jpeg-dir=/usr/local/work/jpeg-6b

make && make install

</pre></code>

p(notice). *Note:* php.ini will be setup later.

---

If you successfully completed these steps, you've now got the platform for [[SWiK Source]] to run. Please continue to the next step: SWiK Source {{Setup and Deployment}}.

[[SWiK Source]] is built on and integrated with the platform combination of PHP, MySQL, and Apache HTTPd. These applications are not packaged as part of the distribution, however SWiK Source requires these and other 3rd party open source components to run properly.

List of components you must either have or obtain and install before setting up SWiK Source:

# [[PHP]] 5.0 (see "below for specific configure line":#buildphp)

# [[Apache]] 2.0

# [[MySQL]] 4.1

# [[Ruby]]

# [[Java]]

# [[libxml]]

# "libjpg":http://www.ijg.org/files/jpegsrc.v6b.tar.gz "libpng":http://www.ijg.org/files/jpegsrc.v6b.tar.gz

# "libpng":http://heanet.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.6rc5.tar.gz "libjpg":http://heanet.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.6rc5.tar.gz

Install these components yourself, or look down for how to compile these from source.

After you have completed installation of these components, continue to {{Setup and Deployment}}.

<br>

h2. Step by step instructions for downloading and installing components

p(notice). *Note:* These instructions assume you will make a directory called /usr/local/work and

do your downloads and installations from there. If you deviate from this, please be careful to note instructions specific to this install directory.

p(notice). *Note:* Many of these steps involve installing and configuring system level software, as such the steps assume that you are running as root. ("su -", "sudo bash", etc). If you are concerned about running as root, you can run much of the configuration without the privilege but please note steps that will have system level impact and do sudo accordingly.

Finally, all the steps assume you are setting your wiki up on a clean machine. If you have previous installations of components, you'll have to adjust these instructions accordingly to make sure that your installations match the dependencies.

If you are using a package management system (such as yum on CentOS or Fedora) you can just make sure you've got the right packages installed, skipping all the following steps. For a CentOS 4.3 install, we used the following packages:

php-5.0.4-5.centos4

php-pear-5.0.4-5.centos4

php-ldap-5.0.4-5.centos4

php-mysql-5.0.4-5.centos4

php-mbstring-5.0.4-5.centos4

php-xml-5.0.4-5.centos4

php-imap-5.0.4-5.centos4

php-gd-5.0.4-5.centos4

php-xmlrpc-5.0.4-5.centos4

php-devel-5.0.4-5.centos4

httpd-suexec-2.0.52-22.ent.centos4

httpd-2.0.52-22.ent.centos4

httpd-devel-2.0.52-22.ent.centos4

mysqlclient10-3.23.58-4.RHEL4.1

mysql-4.1.20-1.RHEL4.1

mysql-server-4.1.20-1.RHEL4.1

On RedHat based systems, you can verify these are installed using 'rpm -qa | grep [php|httpd|mysql]'

<br>

For installation on Ubuntu, here are the package matches discovered so far:

php-5.0.4-5.centos4 - *php5*

php-pear-5.0.4-5.centos4 - *php-pear*

php-ldap-5.0.4-5.centos4 - *php5-ldap*

php-mysql-5.0.4-5.centos4 - *php5-mysql*

php-mbstring-5.0.4-5.centos4 - - *libapache2-mod-php5*

php-xml-5.0.4-5.centos4 - *php-xml-parser* (?)

php-imap-5.0.4-5.centos4 - *php5-imap*

php-gd-5.0.4-5.centos4 - *php5-gd*

php-xmlrpc-5.0.4-5.centos4 - *php5-xmlrpc*

php-devel-5.0.4-5.centos4 - *php5-dev* (?)

httpd-suexec-2.0.52-22.ent.centos4 - - *apache2-mpm-perchild* (?)

httpd-2.0.52-22.ent.centos4 - - *apache2* (?)

httpd-devel-2.0.52-22.ent.centos4 - *apache2-utils* (?)

mysqlclient10-3.23.58-4.RHEL4.1 - *mysql-client*

mysql-4.1.20-1.RHEL4.1 - *mysql-common* (?)

mysql-server-4.1.20-1.RHEL4.1 - *mysql-server*

<br>

h3. *Step 1: Download*

These are the primary versions which have been fully tested for SWiK Source. It should be fine to use new minor release, but some higher point releases may break.

* httpd-2.0.54.tar.bz2 - A new point release or slightly older release should be fine. There may be issues with 2.2 branch however. "Distribution":http://archive.apache.org/dist/httpd/

* php-5.0.4.tar.bz2 - There may be issues with 5.1. branch, 4.x or early releases will not work at all. "Distribution":http://www.php.net/releases.php

* libxml2-2.6.17.tar.gz - "ftp://ftp.xmlsoft.org/libxml2/libxml2-2.6.17.tar.gz":ftp://ftp.xmlsoft.org/libxml2/libxml2-2.6.17.tar.gz

* mysql-standard-4.1.12 - There may be issues with the 5.0 branch. "Distributions":http://dev.mysql.com/downloads/index.html

<br>

h3. *Step 2: Install MySQL*

Run the installer. The installer puts everything in /usr/local/mysql-blahblah and links to it from /usr/local/mysql. Set a root password!, or not (it's a lot easier to manipulate data when you don't ... sure is a lot more secure when you do).

<br>

h3. *Step 3: Install Apache2*

cd /usr/local/work

tar xfj httpd-2.0.54.tar.bz2

cd httpd-2.0.54

./configure --prefix=/usr/local/apache2 --enable-so --enable-rewrite=shared --with-mpm=prefork --enable-expires=shared

make && make install

p(notice). *Note:* The httpd.conf will be configured later, when setting up and deploying the wiki.

<br>

h3. *Step 4: Build and Install libxml2*

cd /usr/local/work

tar xfz libxml2-2.6.17.tar.gz

cd libxml2-2.6.17

./configure --prefix=/usr/local

make && make install

<br>

h3. *Step 5: Download the Graphics Libraries*

The JPEG and PNG libraries for working with images need to be downloaded.

<pre><code>

cd /usr/local/work

curl -O http://www.ijg.org/files/jpegsrc.v6b.tar.gz

curl -O http://heanet.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.6rc5.tar.gz

gnutar xzf jpegsrc.v6b.tar.gz

gnutar xzf libpng-1.2.6rc5.tar.gz

</code></pre>

<br>

h3. *Step 6: Build and Install the JPEG library*

* Build and install the jpeg-6b library:

<pre><code>

cd jpeg-6b

./configure

make install

make install-lib

ranlib /usr/local/lib/libjpeg.a

cd ..

</code></pre>

<br>

h3. *Step 7: Build and Install the PNG library*

* First copy the correct makefile for your environment (.darwin for osx, .linux for linux, etc).

cd libpng-1.2.6rc5

cp scripts/makefile.your_environment ./Makefile

You need to make a few changes to the Makefile to point at your zlib locations before you build the library.

EDITOR_PROGRAM Makefile

* Find the following lines:

<pre><code>

# Where the zlib library and include files are located

#ZLIBLIB=/usr/local/lib

#ZLIBINC=/usr/local/include

ZLIBLIB=../zlib

ZLIBINC=../zlib

</pre></code>

* Reverse the comments to this:

<pre><code>

# Where the zlib library and include files are located

ZLIBLIB=/usr/local/lib

ZLIBINC=/usr/local/include

#ZLIBLIB=../zlib

#ZLIBINC=../zlib

</pre></code>

* Now build and install the PNG library:

make

make install

ranlib /usr/local/lib/libpng.a

<h3 style='margin-top:3em;' id='buildphp'>Step 8: Build PHP</h3>

<pre><code>

cd /usr/local/work

tar xfj ~/php-5.0.4.tar.bz2

cd php-5.0.4

./configure --prefix=/usr/local/php5

--with-apxs2=/usr/local/apache2/bin/apxs

--with-mysqli=/usr/local/mysql/bin/mysql_config --with-mysql=/usr/local/mysql

--enable-mbstring --enable-mbregex --enable-soap --with-libxml2=/usr/local

--with-zlib=/usr --with-iconv --with-gd --with-jpeg-dir=/usr/local/work/jpeg-6b

make && make install

</pre></code>

p(notice). *Note:* php.ini will be setup later.

---

If you successfully completed these steps, you've now got the platform for [[SWiK Source]] to run. Please continue to the next step: SWiK Source {{Setup and Deployment}}.

[[SWiK Source]] is built on and integrated with the platform combination of PHP, MySQL, and Apache HTTPd. These applications are not packaged as part of the distribution, however SWiK Source requires these and other 3rd party open source components to run properly.

List of components you must either have or obtain and install before setting up SWiK Source:

# [[PHP]] 5.0 (see "below for specific configure line":#buildphp)

# [[Apache]] 2.0

# [[MySQL]] 4.1

# [[Ruby]]

# [[Java]]

# [[libxml]]

# "libpng":http://www.ijg.org/files/jpegsrc.v6b.tar.gz

# "libjpg":http://heanet.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.6rc5.tar.gz

Install these components yourself, or look down for how to compile these from source.

After you have completed installation of these components, continue to {{Setup and Deployment}}.

<br>

h2. Step by step instructions for downloading and installing components

p(notice). *Note:* These instructions assume you will make a directory called /usr/local/work and

do your downloads and installations from there. If you deviate from this, please be careful to note instructions specific to this install directory.

p(notice). *Note:* Many of these steps involve installing and configuring system level software, as such the steps assume that you are running as root. ("su -", "sudo bash", etc). If you are concerned about running as root, you can run much of the configuration without the privilege but please note steps that will have system level impact and do sudo accordingly.

Finally, all the steps assume you are setting your wiki up on a clean machine. If you have previous installations of components, you'll have to adjust these instructions accordingly to make sure that your installations match the dependencies.

If you are using a package management system (such as yum on CentOS or Fedora) you can just make sure you've got the right packages installed, skipping all the following steps. For a CentOS 4.3 install, we used the following packages:

php-5.0.4-5.centos4

php-pear-5.0.4-5.centos4

php-ldap-5.0.4-5.centos4

php-mysql-5.0.4-5.centos4

php-mbstring-5.0.4-5.centos4

php-xml-5.0.4-5.centos4

php-imap-5.0.4-5.centos4

php-gd-5.0.4-5.centos4

php-xmlrpc-5.0.4-5.centos4

php-devel-5.0.4-5.centos4

httpd-suexec-2.0.52-22.ent.centos4

httpd-2.0.52-22.ent.centos4

httpd-devel-2.0.52-22.ent.centos4

mysqlclient10-3.23.58-4.RHEL4.1

mysql-4.1.20-1.RHEL4.1

mysql-server-4.1.20-1.RHEL4.1

On RedHat based systems, you can verify these are installed using 'rpm -qa | grep [php|httpd|mysql]'

<br>

For installation on Ubuntu, here are the package matches discovered so far:

php-5.0.4-5.centos4 - *php5*

php-pear-5.0.4-5.centos4 - *php-pear*

php-ldap-5.0.4-5.centos4 - *php5-ldap*

php-mysql-5.0.4-5.centos4 - *php5-mysql*

php-mbstring-5.0.4-5.centos4 - - *libapache2-mod-php5*

php-xml-5.0.4-5.centos4 - *php-xml-parser* (?)

php-imap-5.0.4-5.centos4 - *php5-imap*

php-gd-5.0.4-5.centos4 - *php5-gd*

php-xmlrpc-5.0.4-5.centos4 - *php5-xmlrpc*

php-devel-5.0.4-5.centos4 - *php5-dev* (?)

httpd-suexec-2.0.52-22.ent.centos4 - - *apache2-mpm-perchild* (?)

httpd-2.0.52-22.ent.centos4 - - *apache2* (?)

httpd-devel-2.0.52-22.ent.centos4 - *apache2-utils* (?)

mysqlclient10-3.23.58-4.RHEL4.1 - *mysql-client*

mysql-4.1.20-1.RHEL4.1 - *mysql-common* (?) *UNKNOWN*

mysql-server-4.1.20-1.RHEL4.1 - *mysql-server*

<br>

h3. *Step 1: Download*

These are the primary versions which have been fully tested for SWiK Source. It should be fine to use new minor release, but some higher point releases may break.

* httpd-2.0.54.tar.bz2 - A new point release or slightly older release should be fine. There may be issues with 2.2 branch however. "Distribution":http://archive.apache.org/dist/httpd/

* php-5.0.4.tar.bz2 - There may be issues with 5.1. branch, 4.x or early releases will not work at all. "Distribution":http://www.php.net/releases.php

* libxml2-2.6.17.tar.gz - "ftp://ftp.xmlsoft.org/libxml2/libxml2-2.6.17.tar.gz":ftp://ftp.xmlsoft.org/libxml2/libxml2-2.6.17.tar.gz

* mysql-standard-4.1.12 - There may be issues with the 5.0 branch. "Distributions":http: