From ArchWiki
Revision as of 15:33, 7 June 2012 by Giddie (talk | contribs) (Starting to write up Foswiki installation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Foswiki is a free enterprise collaboration platform written in Perl; developed, supported and maintained by its users and the open-source community.

More information:

You may also be interested in XWiki, which caters to similar needs, but is Java-based.


Note: User intervention is currently required on every Foswiki upgrade. For this reason, I abandoned the idea of adopting and maintaining the foswiki package on the AUR.
Note: These instructions assume you will be using the directory /srv/http/foswiki to store your Foswiki installation.

The Foswiki Installation Guide is very thorough (maybe a bit too thorough), and makes an excellent reference. Follow along using the official guide, but you will find these notes to be more concise, and more specific to ArchLinux.

  • From the Foswiki website, determine the URL of the latest Foswiki release.
  • Become the http user. If you're not sure how to do this, you could try: sudo su -s /bin/bash - http.
  • As the http user, create a temporary directory and unpack the archive:
$ mkdir /tmp/foswiki
$ cd /tmp/foswiki
$ wget <foswiki-url>
$ tar xzf Fos*
$ rm *.tgz
  • Now, as root, move the archive into place in /srv/http:
# mv /tmp/foswiki/* /srv/http/foswiki
# rmdir /tmp/foswiki
# cd /srv/http/foswiki
If you like to determine whether the files already have the correct permissions, you can make use of find to test permissions against the example commands listed in the above Foswiki guide. For instance, this will find any directories that do not have their access mode set to 755:
$ find . -type d \! -perm 755
As of version 1.1.5, I found that only one file was incorrectly set to be owner-writable in error; all other files appeared to have the correct permissions fresh out of the archive. The following command can be used to set the correct permissions (still as root), and will also catch any similar files that may display the same issue in future:
# find pub data -name '*,v' -type f -exec chmod 444 {} \;
Warning: Work in progress. More to follow. Don't miss the next episode—coming soon!