Difference between revisions of "Foswiki"

From ArchWiki
Jump to: navigation, search
(Installation)
(Installation: Condensing and simplifying slightly)
Line 12: Line 12:
 
== Installation ==
 
== Installation ==
  
{{Note|User intervention is currently required on every Foswiki upgrade.  For this reason, I abandoned the idea of adopting and maintaining the {{ic|foswiki}} package on the AUR.}}
+
{{Note|I abandoned the idea of adopting and maintaining the {{ic|foswiki}} package on the AUR for the following reasons:
 +
* Foswiki currently requires some user intervention on every upgrade.
 +
* Foswiki has a convenient mechanism for installing, updating, and removing plugins that does not function unless the installation directory is writeable.}}
  
{{Note|These instructions assume you will be using the directory {{ic|/srv/http/foswiki}} to store your Foswiki installation.}}
+
These instructions assume you will be using the directory {{ic|/srv/http/foswiki}} to store your Foswiki installation.
  
 
The [http://foswiki.org/System/InstallationGuide Foswiki Installation Guide] is very thorough (although maybe a bit overwhelming), 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.
 
The [http://foswiki.org/System/InstallationGuide Foswiki Installation Guide] is very thorough (although maybe a bit overwhelming), 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 [http://foswiki.org Foswiki website], determine the URL of the latest Foswiki release.
 
* From the [http://foswiki.org Foswiki website], determine the URL of the latest Foswiki release.
* Become the {{ic|http}} user.  If you are not sure how to do this, you could try: {{ic|sudo su -s /bin/bash - http}}.
+
* Download and unpack the archive as the {{ic|http}} user at {{ic|/srv/http/foswiki}}. For instance (as {{ic|root}}):
* As the {{ic|http}} user, create a temporary directory and unpack the archive:
+
 
{{bc|
 
{{bc|
 +
# su -s /bin/bash - http
 
$ mkdir /tmp/foswiki
 
$ mkdir /tmp/foswiki
 
$ cd /tmp/foswiki
 
$ cd /tmp/foswiki
$ wget <foswiki-url>
+
$ wget <archive-url>
 
$ tar xzf Fos*
 
$ tar xzf Fos*
 
$ rm *.tgz
 
$ rm *.tgz
}}
+
$ exit
* Now, as {{ic|root}}, move the archive into place in {{ic|/srv/http}}:
+
{{bc|
+
 
# mv /tmp/foswiki/* /srv/http/foswiki
 
# mv /tmp/foswiki/* /srv/http/foswiki
 
# rmdir /tmp/foswiki
 
# rmdir /tmp/foswiki
 
# cd /srv/http/foswiki
 
# cd /srv/http/foswiki
 
}}
 
}}
* Depending on how keen you are on locking down access to the Foswiki installation, you could restrict access to this directory:
+
* Depending on how keen you are on locking down access to the Foswiki installation, you could restrict access to the installation directory:
 
{{bc|
 
{{bc|
 
# chmod o-rx .
 
# chmod o-rx .
Line 40: Line 40:
 
* At this point, you want to ensure that all the files have the correct permissions.  (See the Foswiki guide on [http://foswiki.org/Support.SettingFileAccessRightsLinuxUnix Setting File Access Permissions] for details.)
 
* At this point, you want to ensure that all the files have the correct permissions.  (See the Foswiki guide on [http://foswiki.org/Support.SettingFileAccessRightsLinuxUnix Setting File Access Permissions] for details.)
  
:If you would like to determine whether the files already have the correct permissions, you can make use of {{ic|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:
+
:If you would like to determine whether the files already have the correct permissions, you can make use of {{ic|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:
 
{{bc|
 
{{bc|
$ find . -type d \! -perm 755
+
# find . -type d \! -perm 755
 
}}
 
}}
  

Revision as of 19:51, 8 June 2012

This template has only maintenance purposes. For linking to local translations please use interlanguage links, see Help:i18n#Interlanguage links.


Local languages: Català – Dansk – English – Español – Esperanto – Hrvatski – Indonesia – Italiano – Lietuviškai – Magyar – Nederlands – Norsk Bokmål – Polski – Português – Slovenský – Česky – Ελληνικά – Български – Русский – Српски – Українська – עברית – العربية – ไทย – 日本語 – 正體中文 – 简体中文 – 한국어


External languages (all articles in these languages should be moved to the external wiki): Deutsch – Français – Română – Suomi – Svenska – Tiếng Việt – Türkçe – فارسی

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.

Installation

Note: I abandoned the idea of adopting and maintaining the foswiki package on the AUR for the following reasons:
  • Foswiki currently requires some user intervention on every upgrade.
  • Foswiki has a convenient mechanism for installing, updating, and removing plugins that does not function unless the installation directory is writeable.

These instructions assume you will be using the directory /srv/http/foswiki to store your Foswiki installation.

The Foswiki Installation Guide is very thorough (although maybe a bit overwhelming), 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.
  • Download and unpack the archive as the http user at /srv/http/foswiki. For instance (as root):
# su -s /bin/bash - http
$ mkdir /tmp/foswiki
$ cd /tmp/foswiki
$ wget <archive-url>
$ tar xzf Fos*
$ rm *.tgz
$ exit
# mv /tmp/foswiki/* /srv/http/foswiki
# rmdir /tmp/foswiki
# cd /srv/http/foswiki
  • Depending on how keen you are on locking down access to the Foswiki installation, you could restrict access to the installation directory:
# chmod o-rx .
  • At this point, you want to ensure that all the files have the correct permissions. (See the Foswiki guide on Setting File Access Permissions for details.)
If you would 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; 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 (either as root or http), 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 {} \;
  • Copy bin/LocalLib.cfg.txt to bin/LocalLib.cfg, ensuring that ownership and access rights are identical to the original file.
  • Edit your newly copied file so that the $foswikiLibPath line reads as follows:
$foswikiLibPath = '/srv/http/foswiki/lib'
Warning: Work in progress. More to follow. The next episode is coming soon.