Tags:
installation3Add my vote for this tag create new tag
, view all tags

ALERT! NOTE: The RPM installer is proprietary and is no longer maintained. It is not recommended to use this older release for production use. We are looking for a contributor who can maintain open source installers.

Source: TWikiInstaller Section: rpm

TWiki 4 Installation on RedHat, Fedora and CentOS

This guide explains how to install a Linux with TWiki4 on RedHat type distributions such as RedHat Enterprice Linux 4 (RHEL4), Fedora Core 4 and 5 (FC4 and FC5) and CentOS 4. For those unfamiliar with CentOS, CentOS is a clone of RedHat. It is built from the original RedHat source RPMs and anything that runs on RHEL will run on CentOS. The only difference is that CentOS does not charge any fees for updates, it has no support other than community support and all RedHat logos and branding has been replaced by Centos' own. Any RPMs made for RHEL4 can be used on CentOS 4. And any RHEL5 RPM can be used on Centos 5.

Installers on RedHat should also note that there is an experimental installer available at TWikiInstaller.

Installation of RHEL, Fedora or CentOS

  • When you install the Linux you will be asked which type of installation you want. Personally I always choose "Everything", but you will get the required software installed by choosing both "Software Development" and "WebServer". (Note: FC5 does not have the "Everything" option).
  • You are installing a web server so your Linux box must be setup with fixed IP address.
  • The Linux box will need to send emails so it must have access DNS to be able to look up email addresses.
  • The Firewall should be activated but with port 80 open to the world. This is suggested during initial installation.
  • SELinux can be enabled but it is not easy to setup so TWiki is working. You can choose to turn it off but there is a very good guide for how to setup SELinux on TWikiOnSELinux.
  • It is always recommended to have a router between the public Internet and the Webserver and then forward only port 80 to the webserver. The webserver is then setup with a local fixed IP address. If your webserver is on an Intranet serving only internal clients you are for sure already on a router protected from the wild public Internet. Then all you need is a fixed IP address and a local domain name.

In the following we will be assuming that you are the administrator of the RH/Fedora/Centos Linux box and have root access. Most of the steps requires that you run the commands as root.

Activate the Apache server

Many of these procedure can be done via a GUI, but it is so much easier to do from a terminal when you follow a guide like this

As root you do these steps

  • Activate the Apache server: service httpd start
  • Enable the Apache server also after reboots: chkconfig --levels 345 httpd on

  • Check that the server is running by opening a browser and look up http://localhost/
    What you should see is a default test page.
  • Check that the server can be accessed from another machine by looking up the IP address (or domain name if available) from another client machine. Again what you should see is a default test page.

Install the CPAN modules required by TWiki

You should install the following CPAN modules which are required by TWiki and the most popular plugins. This list is a little longer than actually required by the basic TWiki installation but sooner or later you will want to install some of the more popular plugins and then it is nice to already have the necessary CPAN modules installed.

CPAN modules are Perl libraries that are well tested and made standard. Your RHEL/Fedora/Centos already have many installed but the onces in the list below are not installed per default.

There are at least 4 ways to install CPAN modules

  1. Download the source package from CPAN and build it manually.
  2. Easy but not always possible: Install the using the CPAN modules which builds and installs it all for you. First time you run it you will be asked a lot of questions that set it up. It can be a little tricky to get to work if you are behind a firewall that requires authentication.
  3. Download and install RPM modules. Since you are running a RedHat type Linux it make most sense to download and install RPMs. That also makes it easy to later upgrade the modules to newer versions. So this is the method the author of this document recommends.
  4. Very similar to 3. You can use yum to install them. I presume that when this was initially written they were not in the repositories. The following syntax worked for me (do it once for each of the six modules):
yum install perl-FreezeThaw

These are the CPAN modules that are recommended to install

  • CGI::Session - Needed for TWiki's session feature which is really a must have
  • Error - Needed if you later want to develop plugins. It is also distributed with TWiki but the author has experienced lots of trouble with the build script that builds plugins which sometimes cannot find this library. By adding it to the site Perl library you avoid this kind of trouble.
  • FreezeThaw - an indirectly needed module used by other modules.
  • GD - Used by the pluging that can produce graphics such as TWiki:Plugins.TWikiDrawPlugin. It requires that lib gd is installed. If your choice of installation does not include you simply need to install the rpms gd and gd-devel. They are both on the CDs or DVD.
  • HTML::Tree - Needed by some popular plugins
  • Time-modules (Time::CTime, Time::DaysInMonth, Time::JulianDay, Time::ParseDate, Time::Timezone) also needed by some popular plugins.

If your already installed RHEL/Fedora/CentOS was not installed as "Software Development" and "WebServer" you may need to install additional modules. TWikiSystemRequirements lists the modules requires for a basic installation and shows how to test which ones you have. A few examples of this.

  • To check for perl module Filehandle: perl -e 'use FileHandle; print $FileHandle::VERSION."\n"'
  • To check perl module Time::Local: perl -e 'use Time::Local; print $Time::Local::VERSION."\n"'

Install CPAN modules manually

(difficult - only if you have to).

First we download them

Then we install them. This is done more or less the same way with all of them. At least one module depends on FreezeThaw so install that first.

  • Untar the package in some temporary directory with tar -zxvf filename.tar.gz
  • Run these commands (look in the readme file - maybe there are extra steps

   perl Makefile.PL
   make
   make test
   make install

  • You can delete the entire directory with the sources afterwards if you desire.

Install CPAN modules with CPAN.pm module

(easy but not always possible)

First time you run the CPAN module it will ask for a lot of things of which you probably have no idea. The good thing is that all you need to do is answer all the default values by hitting enter except when it asks you for the part of the world, and the country. Finally it lists a number of CPAN mirrors in your country with a number in front. Just add 3-5 of them. If one is with your own ISP add that as the first on the list.

Make sure you install the FreezeThaw module first as other modules may depend on it.

The generic command to install a module called Chocolate::Belgian is

perl -MCPAN -e 'install Chocolate::Belgian' 

So to install the recommended modules you run

perl -MCPAN -e 'install FreezeThaw'
perl -MCPAN -e 'install CGI::Session'
perl -MCPAN -e 'install Error' 
perl -MCPAN -e 'install GD' 
perl -MCPAN -e 'install HTML::Tree' 
perl -MCPAN -e 'install Time-modules'

Install CPAN modules from RPM

(easy and recommended by the author of this topic)

The missing CPAN modules are not on the CDs or DVD and I have not found them on RedHat's, Fedora's or Centos' sites either. But Dag Wieers has them all in his collection and they are kept pretty up to date. Simply download the RPMs and put them all in the same directory.

The URLs contains a couple of versions and packages for both RedHat and Fedora. For RHEL and CentOS simply use the newest 'el4' package. For Fedora use the latest Fedora package. For Fedora 5 the 'el4' is probably the best if there is no fc4, or fc5 version. Since these are Perl modules it is not as critical as with binary packages.

From the directory in which you have the 6 rpm files simply run

rpm -ivh *

This installs all of them at once.

If you later want to update one of them to a newer version you use rpm -Uvh filename.rpm

There has been a report that the RPM package perl-DBD-Pg may be missing RHEL 4. In Centos it is on the CDs/DVD and on the official repositories so you should be able to install it from there is it shows up as a missing dependency.

Create the TWiki directory

You will see many examples on TWiki.org where TWiki is installed in the Apache DocumentRoot (which in RedHat/Fedora/Centos is /var/www/html). This is not a good idea because this means that all the directories are per default accessible from the web and we will have to disable the access. You will also see examples where the TWiki installation is placed below some user's name. This means that the unpriviledged Apache user can read any file from this users home directory and that is not a good idea either. The best is to place the TWiki installation in a place where Apache has access but not in the DocumentRoot directory. A good choice for RedHat/Fedora/Centos is /var/www/twiki.

mkdir /var/www/twiki

Download TWiki and any additional hotfixes and unpack them

VERSION is the current version number like e.g. 4.0.4 for TWiki and 4.0.4-2 for hotfix 2

  • Download TWiki from TWiki:Codev.DownloadTWiki. Choose the tgz file.
  • Download the latest hotfix package if one is released (it will be linked from TWiki:Codev.DownloadTWiki)
  • Move both TWiki-VERSION.tgz and hotfix-VERSION.tgz to /var/www/twiki
  • Unpack first TWiki. tar -zxvf TWiki-VERSION.tgz
  • Now unpack on top of the already unpacked TWiki tree so files get replaced tar -zxvf hotfix-VERSION.tgz
  • You can now delete the two tgz files or move them somewhere else.

Create an Apache config file

The key element in any type of security is to start with having an overview. Spreading small .htaccess files all over the place is not the ideal way to have an overview. The best thing is to keep everything related to TWiki in one easy to overview Apache config file which is included from the main Apache config file.

RedHat/Fedora/CentOS keeps the Apache config file in /etc/httpd/conf/httpd.conf. Inside httpd.conf you will find a statement Include conf.d/*.conf. This means that all files that ends with .conf in the /etc/httpd/conf.d directory are included. We take advantage of this and create a file /etc/httpd/conf.d/twiki.conf which contains all the settings for TWiki.

If you have multiple virtual hosts defined in httpd.conf then you should know that certain Apache features such as rewrite will not work unless they are defined within the scope of the virtual host. This is easy to overcome.

Instead of the filename twiki.conf we give it a different suffix so it does not get included in the global apache config context. We can call the file twiki.config instead. And then include this file from within the virtual host definition in httpd.conf

Example

<VirtualHost *:80>
    ServerName mydomain.dk
    ServerAlias *.mydomain.dk
    DocumentRoot /var/www/mydomain/html
    Include conf.d/twiki.config
</VirtualHost>

Now let us make that twiki.conf file. We assume you know how to create a new file from a text editor. To make the content of twiki.conf we use the TWiki:TWiki.ApacheConfigGenerator.

  • The default twiki root directory /var/www/twiki is fine
  • Enter the IP address range or hostnames that will have access to configure. It is essential that the configure script is protected either by IP address or by username/password. To get started without too much problems protecting by IP address is a good idea. If you work locally on the machine simply put 127.0.0.1 in this field. If you setup the machine from a remote client use the IP address of this remote client instead.
  • Enter the list of user names that are allowed to view configure. For this to work you need a .htpasswd file with a username and a password. Later when TWiki is fully installed TWiki and provided that you have chosen to authenticate with Apache .htpasswd type authentication this .htpasswd file will be created by TWiki. But at this point we have a "chicken and the egg" situation. So you have 3 options
    • Disable authentication of configure until you have done the first configuration
    • Enable all access from the computer you are installing from by IP address
    • Create a temporary user in a .htpasswd file. If you choose a user name that you later want to use in TWiki then you will need to remove this username again from .htpasswd before you attempt to register because otherwise TWiki will reject the registration because your name is already in the .htpasswd file.
  • Enable mod_perl? You are adviced to startup without mod_perl. Mod_perl means that Apache preloads the TWiki code and keep it compiled in RAM. This can make TWiki twice as fast as without. But it also requires that the perl code is written without any uninitialized global variables. Not all plugins fulfills this requirement. Start without. Then you can try enabling it later by revisiting the TWiki:TWiki.ApacheConfigGenerator.
  • Choose your Login Manager. Here you have to make an important choice. Do not choose None!
    • TemplateLogin - Redirect to the login template, which asks for a username and password in a form. This is easy to get to work. But if you later want to authenticate using an LDAP server or similar you cannot use this method. The author of this document does not like the current implementation of TemplateLogin because especially Internet Explorer think that each URL within TWiki is new and cannot remember username and password. The result is that you are prompted all the time without username and password autofilled. TemplateLogin is by far the most pretty way to login.
    • ApacheLogin - Apache is configured to ask for authorization information. This is a very plain authentication where Apache asks the browser to authenticate. The browser presents the user with the standard small pop-up window with username and password fields. With this methpd even Internet Explorer has no problem with remembering username and password.
  • Choose which PHP version you have installed. Unless you have a very old RedHat the answer is always "PHP4/5 Installed". Even though TWiki has nothing to do with PHP - we need to make sure that all execution of PHP scripts are disabled in the directory in which TWiki keeps file attachments. Otherwise you have a major security issue.
  • Finally you choose two counter measures against spam. If your TWiki will be on the public Internet turn these on. If it is only on an Intranet you do not want to activate this protection as it put some limits to the use of TWiki with respect to which types of attachments you can upload.
  • Click the "Update config" button. You can now copy paste an entire twiki.conf from the text area and into your twiki.conf file. Save the file.
  • Change the access right and ownership of the twiki config file.
    • chmod 644 twiki.conf
    • chown root:root twiki.conf

Setting the Library path in bin/LocalLib.cfg

The next step it to tell the TWiki CGI scripts where to find the rest of TWiki.

  • Go to the /var/www/twiki/bin directory
  • Copy the file LocalLib.cfg.txt to LocalLib.cfg. cp LocalLib.cfg.txt LocalLib.cfg
  • Open the file with a text editor.
  • Change the line $twikiLibPath = "/absolute/path/to/your/lib"; to $twikiLibPath = "/var/www/twiki/lib";
  • Save the file.

Change the ownership of twiki to Apache

Now we change the ownership of the entire twiki directory tree to Apache. We change both owner and group. On RHEL/Fedora/Centos Apache runs with username apache and group name apache.

  • chown -R apache:apache /var/www/twiki

Set the file and directory access rights

If you followed the advice so far and installed the .tgz file the access rights should be correct. However if you are in doubt or you accidently have altered the access rights then go to TWiki:TWiki.SettingFileAccessRightsLinuxUnix. Here you will find a script you can run which sets all the access rights back to the default recommended.

Note that there is a difference between access rights for files and for directories. For Apache to be able to access files in a subdirectory all the parent directories must be "redable and executable" to the world assuming the owner is normally root. Ie. the access rights of /var and /var/www must be 755. When people chose to place the twiki directory a different place - typically under a user - failing to have world executable but enabled on the parent directories is the main reason why nothing works.

Restart the Apache server

It is now time to restart the Apache server so we read in the TWiki config file.

  • service httpd restart

Run configure first time

From a browser look up the following URL.

If you are using another client machine replace localhost with the IP address or domain name of the webserver.

You should now see the TWiki configure script. First time you run it it will have a very limited set of settings. The only settings you can see are the ones below the "General Path Setting" bar.

  • Check that the default URL host is correct with the correct domain name that people will use when they access the server.
  • Ignore all other settings and errors for now and go to the bottom and hit "Next".
  • Define a configure password. This password has nothing to do with the admin user password you later use in TWiki and it has nothing to do with any username/password you may have setup to protect the access to configure. This password is just an extra protection against saving settings in configure. But it is not secure enough to leave configure accessible to the public which is why we protected it earlier by IP address or username. Note that it is the lower part of the screen where you define a new password and you have to enter it twice.
  • You now get back to configure. All the errors should now be gone and we are ready to setup the rest of TWiki.

Configure - Setting up security

Hit the Security Setup bar. We now walk through the steps in this important section and give recommendations. The ones in bold are the ones where you may have to change something.

  • {UseClientSessions} - YES! Life is so much easier for the users when Client Sessions are enabled.
  • {Sessions}{ExpireAfter} - Set this to a negative number. A good value is -21600. TWiki becomes a crawling snail if this number is positive because it means that it cleans our sessions each time someone views a page. Instead we will purge the session files with a cron job. We get back to that later.
  • {Sessions}{IDsInURLs} - Leave this off
  • {Sessions}{UseIPMatching} - Leave this on
  • {Sessions}{MapIP2SID} - Leave this off
  • {LoginManager} - We discussed this earlier when we created twiki.conf. Choose the LoginManager that matches your preference.
  • {DefaultUserLogin} - Leave this as "guest"
  • {DefaultUserWikiName} - Leave this as "TWikiGuest"
  • {AdminUserWikiName} - Leave this as "TWikiAdminGroup"
  • {SuperAdminGroup} - Leave this as "TWikiAdminGroup"
  • {UsersTopicName} - Leave this as "TWikiUsers"
  • {MapUserToWikiName} - Leave this on! Ignore the help text. Keep this on even if you do not enable users to have login names different from their WikiName. If you turn this off a bug in TWiki prevents users from resetting their password. And some plugins do not work well either. Note from TWiki 4.2.0 the old bug is resolved and this config option has been removed. From 4.2.0 {Register}{AllowLoginName} controls if login is mapped to wikiname.
  • {AuthScripts} - Leave these as default "attach,edit,manage,rename,save,upload,viewauth,rdiffauth".
  • {AuthRealm} - You can leave this as is or change the words to suit your needs. The text is displayed in the username/password window when using ApacheLogin
  • {PasswordManager} - Leave it at TWiki::Users::HtPasswdUser is you have the users passwords stored in a .htpasswd file. If you use LDAP authentication or similar external password manager set this to "None".
  • {MinPasswordLength} - Change this to your preferred policy
  • {Htpasswd}{FileName} - Leave this as default /var/www/twiki/data/.htpasswd. Then you know where you have it and it fits the twiki.conf file we created earlier and we know it is protected from access.
  • {Htpasswd}{Encoding} - The default 'crypt' is probably fine.
  • {UserMappingManager} - There is currently nothing to choose from. Leave it.
  • {Register}{AllowLoginName} - Leave this off if you keep the passwords in the .htpasswd file. If you use an external authentication such as LDAP then your usernames are most likely different from the WikiNames. Then you need to set this ON.
  • {Register}{HidePasswd} - Leave this on.
  • {Register}{NeedVerification} - It may be a good idea to leave this off until you have registered yourself - in case you run into problems with TWiki sending emails. If you run a public TWiki you should go back and enable this once your TWiki is setup and running. For Intranet TWikis leave this off. It is not annoying then.
  • {SafeEnvPath} - Leave as default.
  • {DenyDotDotInclude} - Leave this on.
  • {INCLUDE}{AllowURLs} - For Internets only enable this if you need it. For Intranets turn this ON. It is a nice feature.
  • {AllowInlineScript} - Leave this on.
  • {UploadFilter} - Leave this as default.
  • {NameFilter} - Leave this as default.
  • {ForceUnsafeRegexes} - Leave this off
  • {GetScriptUrlFromCgi} - Leave this off
  • {RemovePortNumber} - Leave this off

Configure - setting up Antispam Measures

  • {AntiSpam}{EmailPadding} - For Internets add some UPPERCASE spam padding word to make it a little more difficult to harvest email addresses. For Intranets turn this feature off.
  • {AntiSpam}{HideUserDetails} - For Internet sites turn this on. For Intranet sites turn it off.
  • {AntiSpam}{RobotsAreWelcome} - Leave this on

Configure - setting up Localisation

TWiki user interface internationalisation (I18N), which means providing a translated TWiki user interface, is an expensive feature with respect to performance. Do not enable it unless it is important that your TWiki works in your local language. And if you enable it - turn only the languages on that you really need.

TWiki content internationalisation, which is mostly about WikiWords and page contents using international characters, has virtually no performance impact and should be enabled if you need it. See InstallationWithI18N for more details on setup, and I18N for other resources.

Mails and proxies

  • {WebMasterEmail} - enter your webmaster email address here. All emails sent from TWiki uses this as the From address so it must be a valid email address. Otherwise emails will bounce back from most mail servers.
  • {MailProgram} is not important. You have Net::SMTP installed by default on your RHEL/Fedoa/Centos
  • {SMTP}{MAILHOST} - Set this to localhost. You can also set it to a local SMTP server
  • {SMTP}{SENDERHOST} - Set this to the registered domain name you have - if you have one.
  • {SMTP}{Username} and {SMTP}{Password} are used when you specify an external {SMTP}{MAILHOST} and this requires authentication

Plugins

  • Enable the ones you think you need. We recommend that you enable them all - except WysiwygPlugin which you should only enable if you accept that it is not a finished perfect tool. Check the TWiki:Plugins web for most recent discussions on which specific WYSIWYG plugin combination is best.

Save your changes

  • Hit the "Next" button at the bottom to save your changes. You will be prompted for the configure password.

Register yourself as a user.

You now register yourself as a user.

  • Open this URL in your browser: http://localhost/twiki/bin/view/TWiki/TWikiRegistration
  • Fill out the form and submit.
  • Note that a WikiName is automatically composed from your First and Last names. This is the username that TWiki knows you as when you are logged in.
  • If you had turned off the {Register}{NeedVerification} in configure you are now registered. Otherwise TWiki will send you a verification code by email and will be presenting you with a page on which you must enter the verification code. If for some reason email does not work, you can find the verification code in the file /var/www/twiki/data/RegistrationApprovals directory. The file there is named as FirstLast.Approval_code. Complete the registration by entering the verification code.

Change your user account to being an administrator.

To become the administrator you simply add yourself to the TWikiAdminGroup.

  • Go to http://localhost/twiki/bin/view/Main/TWikiAdminGroup
  • Hit the edit button.
  • In the line saying * Set GROUP = ATWikiUser replace ATWikiUser by the WikiName you registred
  • In the line saying * #Set ALLOWTOPICCHANGE = TWikiAdminGroup remove the #. This locks the topic so that only you can edit it and add more names to the TWikiAdminGroup.
  • Hit the Save button
  • You are now an administrator on your TWiki.

Cron setup

We need to add a couple of lines to the cron daemon. The cron daemon runs programs according to a schedule. We run a program /var/www/twiki/tools/tick_twiki.pl which cleans out expired session files and remove expired lease files.

In the directory /etc/cron.d directory create a file called twiki

In /etc/cron.d/twiki file add this line to run the tick_twiki.pl every night at 5 o'clock.

0 5 * * * root cd /var/www/twiki/tools && perl -I /var/www/twiki/bin tick_twiki.pl

If you want TWiki to send emails notifying people about topic changes you need a similar line to run mailnotify. Here is an example where we run this script at midnight.

0 0 * * * root cd /var/www/twiki/tools && perl -I /var/www/twiki/bin mailnotify -q

Note that crond refuses to run anything in /etc/cron.d if the file is writable by anyone else than root. So watch out not to change access rights. Access right for files in /etc/cron.d should be 600 or 644.

WIKIWEBMASTER (if upgrading)

From TWiki 4.1 this setting is defined in configure under Mail and Proxies. If you are upgrading from an old TWiki make sure to remove the Set WIKIWEBMASTER... setting from TWikiPreferences.

Other tailoring

Now the fun begins setting up your TWiki with your own logos, adding new webs etc. This is where this topic ends.

Enjoy your new TWiki

Note: This topic previously contained some old out of date discussion about RPMs so I decided to replace it.

-- Contributors: KennethLavrsen, KentPoots

Thanks Kenneth for writing the detailed how-to document, and thanks KentPoots for contributing the base for this document! I put Kent as a contributor even though the doc is a rewrite.

-- PeterThoeny - 26 Sep 2006

Excellent work, Kenneth!

I just ran the guide through and the only things I stumbled into was that I had to install rcs (up2date -i rcs) on this particular server, and that I prefer to keep TWiki cron entries in a file by themselves (using /etc/cron.d).

Not sure if a "time to save your changes!" would be helpful after the last configure section on enabling the plugins, before registering a user - it might just be me making up problems smile

-- SteffenPoulsen - 27 Sep 2006

Excellent inputs. I updated above guide accordingly.

-- KennethLavrsen - 11 Oct 2006

On Red Hat Enterprise Linux 4, in order to load the CPAN Module CGI::Session, I had to install the following CPAN module : DBD-Pg. I downloaded (and later installed) the following file: perl-DBD-Pg-1.31-6.i386.rpm, from the following adress: http://rpmfind.net/linux/rpm2html/search.php?.query=perl-DBD-Pg.

-- DanielLowy - 24 Apr 2007

although following the steps one by one i still encounter premission denied when trying to open the configure page. I also checked the linux permissions page, but still nothing.

-- EranKaufman - 25 May 2007

I've updated the Localisation comments above - there are two parts of I18N and only one has a significant performance impact. I've also made a few formatting fixes.

-- RichardDonkin - 13 Oct 2007

I noticed some out of date advice above about the value for {Sessions}{Dir} - this should be /tmp/twiki to remove a security vulnerability - see http://twiki.org/cgi-bin/view/Codev/SecurityAlert-CVE-2007-0669 for the details.

I've changed the above recommended setting. The default was fixed in TWiki 4.1.1 in any case.

-- RichardDonkin - 19 Nov 2007

Sessions dir is no longer a setting starting from 4.2.0

-- KennethLavrsen - 01 Feb 2008

Regarding Install CPAN modules from RPM: If I download from Dag's and do rpm -ivh * as instructed (even if I also include additional RPMs for DBD-Pg and DBI, which are required by perl-CGI-Session) on a stock RHEL4u6 installation, I get:

warning: perl-CGI-Session-4.20-1.el4.rf.noarch.rpm: V3 DSA signature: NOKEY, key ID 6b8d79e6
error: Failed dependencies:
        libpq.so.3 is needed by perl-DBD-Pg-2.2.2-1.el4.rf.i386
        perl(version) is needed by perl-DBD-Pg-2.2.2-1.el4.rf.i386
        perl(RPC::PlClient) >= 0.2000 is needed by perl-DBI-1.602-1.el4.rf.i386
        perl(RPC::PlServer) >= 0.2001 is needed by perl-DBI-1.602-1.el4.rf.i386

-- JohnDeStefano - 14 Mar 2008

Please add the full path for running the /upgrade_emails.pl script which is under tools directory.

when you are upgrading from cairo sep2004 to 4.x then this script come into place and the way for running is from the twiki/bin directrory as below.

#cd /twiki/bin bin]#perl ../tools/upgrade_emails.pl

and you are done. it would be helpful for the new users who are upgrading first time.

Thank you in advance

-- HakunaMatata - 18 Jun 2008

Thanks for this document. It really helped fill in some gaps while I was installing TWiki (4.2.0) on my Fedora system. However, I ran into a couple of snags, and thought it might help others to know about them.

  1. The instructions for creating the .htpasswd file say "Simply add the username that you will use later when you register yourself on your TWiki." However, when I went to register myself on the TWiki, it thought this name was already registered, and did not create the user page or add it to the list of users. Once I changed the name in the .htpassword file, then I could register myself as a TWiki user. I think the relationship between the initial user created in the .htpasswd file and the first TWiki user could be better explained.
  2. I could not find the "{MapUserToWikiName}" setting in the Security Setup section of the Configure page (or anywhere else on the Configure page). I searched for information about this, and have the impression that perhaps this setting may be deprecated in my version of TWiki, though I am not sure.

In any case, I seem to have successfully installed TWiki, largely with the help of this document. Thanks, again!

-- BryanRaney - 28 Jun 2008

I have done some updates for 4.2.0. I will probably need to walkthrough the whole doc again soon. I plan to do that when we release 4.2.1.

-- KennethLavrsen - 30 Jun 2008

Unfortunately, after having followed this, and the installation guide that shipped with 4.2.0, I have some issue with certain parts of twiki not being recognizing the lib path appended to @INC via /twiki/bin/LocalLib.cfg. The errors are consistently the following:

[Wed Jul 23 16:23:30 2008] [warn] -T switch is ignored, enable with 'PerlSwitches -T' in httpd.conf\n [Wed Jul 23 16:23:30 2008] [error] Can't locate TWiki/UI/Edit.pm in @INC (@INC contains: . /usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.8/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.7/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.6/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl/5.8.7 /usr/lib/perl5/vendor_perl/5.8.6 /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.8.8/i386-linux-thread-multi /usr/lib/perl5/5.8.8 . /etc/httpd) at /var/www/twiki/bin/edit line 31.\nBEGIN failed--compilation aborted at /var/www/twiki/bin/edit line 31.\n

The @INC path looks find in configure, what gives?

AdamKadmon

-- AdamKadmon - 23 Jul 2008

Try raising a Support request, it will have more visibility there. This may be a ModPerl issue given mention of httpd.conf, try without mod_perl first, or see the TWiki.org pages about this.

-- RichardDonkin - 28 Jul 2008

BasicForm
TopicClassification TWikiDeployment
TopicSummary Detailed step by step guide to installing TWiki4 on Redhat/Fedora/Centos
InterestedParties

RelatedTopics TWikiOn, TWikiOnLinux
Edit | Attach | Watch | Print version | History: r41 < r40 < r39 < r38 < r37 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r41 - 2008-08-13 - SvenDowideit
 
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.