This cookbook is intended to get you up and running with TWiki on Windows quickly, with as few problems as possible. The 'cookbook' approach is simply to restrict the many choices that someone installing TWiki must make, so that a reasonably well-defined procedure can be followed - new users can simply follow the steps, while experts can use this as more of a guideline. Please read TWiki:Codev.WindowsModPerlInstallCookbook in case you use mod_perl.
There is a huge volume of existing material on TWiki about installing on Windows, and I'm indebted to the many contributors for this - the aim of this cookbook is to synthesise the many tips into a recipe that works.
-- RichardDonkin? - 24 Feb 2002
binutils
to list of Cygwin packages, and added warning not to use Apache 2.0
SMTPMAILHOST
for user registration and notification
grep
commands in TWiki.cfg
c:/twiki
directory
c:/cygwin
directories) is essential for binary attachment uploads to work properly
egrep
and fgrep
on some Cygwin versions (fix from TWiki:Main.DavidLeBlanc)
c:\temp
, based on comments by TWiki:Main.MaryDeMarco
pcre
to list of Cygwin packages (required by grep
), fixed bug in Apache config (Apache doesn't allow '#' comments on same line as config)
register
script committed to TWiki:Codev.TWikiAlphaRelease - most users can ignore this for now, but the edits in step 5 will eventually go away
uname -a
command to check Cygwin DLL version, and delete Apache config's PassEnv line
register
, fixed minor typo in Cygwin binary mode section, after beta testing by TWiki:Main.JerryWard (thanks!)
This document covers installation of the TWiki Dec 2001 release in the following environment - if you want to use a different environment, feel free to use this as a guideline only.
Component | Name, version | Comment |
---|---|---|
Operating System | Windows 2000 | Should also work for Windows NT |
Web Server | Apache 1.3.26 | Windows-specific security holes fixed in this build (check latest version at http://httpd.apache.org, but don't use Apache 2.0 yet) |
Unix tools | Cygwin 1.3.9 | Simplest way to get a whole set of required tools |
Perl | Cygwin perl-5.6.1-2 | Comes with Cygwin |
RCS | Cygwin rcs-5.7-2 | Comes with Cygwin, includes a file corruption bugfix |
Why this choice of packages? Because I've tried them, and they work well, without requiring a complicated setup... In particular, Apache is the commonest choice for TWiki on Unix/Linux, Cygwin Perl is very close to Unix Perl, and the Cygwin RCS is regularly updated, with a recent TWiki-relevant bug fix in Feb 2002. Cygwin also lets you install the Unix tools, Perl and RCS in a single step, saving quite a lot of time.
More recent minor versions should be OK, but they can introduce bugs.
Major version upgrades, such as Apache 2.0 and Perl 5.8, are very likely to cause problems - for example, Apache 2.0 is unable to authenticate (see TWiki:Support.FailedAuthenticationWithApache2OnWinNT) users created by the current TWiki user registration script (due to a feature being removed in 2.0), and Perl 5.8 may introduce issues due to its Unicode features. Even though the Apache group says that Apache 2.0 is the best version, that's not true for TWiki.
There are doubtless other combinations of components that may work - in particular:
TWiki.cfg
, and is probably a simpler choice if you need an easy way to install mod_perl (see TWiki:Codev.ModPerl). TWiki:Codev.ActiveState Perl can be substituted without too much hassle, and in fact the same TWiki.cfg
can be used for both TWiki:Codev.ActiveState and Cygwin Perl.
Covering the whole range of additional possibilities, particularly web servers, would make this cookbook too complex, and is best handled as a separate activity.
If you already have some of these add-ons installed, here's how to check the versions - this assumes you have TWiki:Codev.CygWin already installed:
$ : Cygwin DLL version is the number in 1.3.x format $ uname -r $ less c:/your-apache-dir/Announcement $ perl -v $ rcs -V
If you have an older version of any component, do yourself a favour and upgrade it as part of the install process.
You will need to have local administrator rights and to be comfortable with Windows administration.
This cookbook is intended for a clean install, i.e. none of these components are already installed. However, since Cygwin and Apache's installation process is fairly upgrade-friendly, upgrades should work as well - take backups of all your data and config files first, though!
Editing Cygwin files is best done with an editor that can handle Unix file format (see the Cygwin binary mode section below) - the installation process includes nano
, a non-GUI editor, but if you prefer to use a GUI editor, you should first install PFE, a freeware editor that supports Unix format files. PFE is available on download.com and Simtel.
Another good TWiki:Codev.OpenSource editor is SciTE (aka WSciTE), available at http://www.scintilla.org/SciTE.html.
It's a little known fact that you can use pathnames such as c:/apache
almost everywhere in Windows - try it in a File Open dialogue box. The main exception is the Win2000 cmd.exe
command line shell - here, you must use double quotes around forward slashes, e.g. dir "c:/apache"
will work fine.
The reason this matters is that '\'
is a special character to Perl and other tools, so it's much easier to use '/'
everywhere.
TWiki:Codev.CygWin is a Unix-like environment for Windows - many of its tools support the c:/apache
format, but it also provides a more Unixlike syntax, e.g. /usr/bin/rcs.exe
, because some Unix tools ported onto Cygwin only support the Unix format.
When you launch a Cygwin shell, your existing PATH variable is translated from the Windows format to the Unix format, and the ';' separators in the Windows PATH are changed into ':' separators as required by Unix. A Cygwin tool (e.g. Cygwin Perl or Cygwin RCS) will always use the Unix PATH format, and will accept Unix format pathnames.
Apache runs as a native Windows process and has nothing to do with Cygwin (at least the version used in this cookbook doesn't). Hence it supports c:/ pathnames in its config files and the first line of Perl CGI scripts.
If you need to use spaces in file names (not recommended), put double quotes around the file name in the httpd.conf
file. There have been some security-related bugs in Apache with long pathnames, which are a bit more likely if you use spaces, so it's best to just avoid long names and using spaces.
Once Perl has been launched by Apache, it is in Cygwin mode, and so is everything it launches, including ls
, egrep
, and RCS tools that it (typically) launches with the bash
shell.
If you need to use spaces in file names (not recommended), you may be able to put double quotes around the file name in the TWiki.cfg
file - however, it's not clear whether all the TWiki code would work with this.
Enough background, let's get on with the installation.
Head to http://twiki.org, click the download link, and fill in the form to request a URL for download. You'll get an automated email, which should arrive by the time you need it.
1. Download Apache
apache_1.3.X-win32-x86-no_src.msi
where 'X' is 20 or higher
instmsi.exe
) from the Apache Win32 download page - this enables you to install .MSI files. You may need to update the .MSI Installer if you have an old version under NT.
2. Install Apache
c:\
as the installation directory - this actually installs Apache into c:\apache
(if you specify c:\apache
, it installs into c:\apache\Apache
). Putting Apache into c:\Program Files
is not recommended for easy editing of Apache config files from Cygwin.
3. Test Apache
apache -k start -n apache
) or standalone (by typing apache -k start
)
Congratulations, you now have a working web server!
To restart Apache after changing its config, type:
apache -k restart
for standalone Apache process running in another window
apache -k restart -n apache
for Apache running as a Win2000 service (-n gives name of service)
Another useful command is apache -k stop
.
4. Install Cygwin
Head to http://cygwin.com, and click the Install Cygwin Now link. Save the setup.exe
in a directory, e.g. c:\download\cygwin-dist
.
Now run the Cygwin setup.exe
file - this will also install Perl and RCS in one fell swoop.
c:\download\cygwin-dist
as the local package directory, and suitable proxy settings, then pick a local mirror site
bash
binutils
diffutils
gcc
grep
gzip
make
nano
ncftp
pcre
perl
(5.6.1-2 or higher)
rcs
(5.7-2 or higher)
tar
textutils
unzip
w32api
wget
(optional, useful for Perl install and TWiki:Codev.ReadWriteOfflineWiki)
lynx
if you are upgrading from an older Cygwin installation (to avoid annoying DLL messages) - if you want Lynx, read the Cygwin FAQ entry and upgrade libncurses5
.
gcc
, which is required for simple installation of Perl modules that use the C language. Something like 20 to 30 MB of free disk space should be enough for Cygwin, but I didn't test this (try a du -k /
after a new install and let me know the last figure).
5. Test Cygwin
bash
shell, which has command line editing features
bash
will 'complete' the name. If bash
beeps at you, hit TAB again to see the files/directories that match the name so far, and type a bit more before hitting TAB. This saves a lot of time!
rcs -V
- you should see the RCS version, 5.7
perl -v
- you should see cygwin mentioned in the first line, and the Perl version, 5.6.1
grep home /etc/passwd
- you should see some output.
The Cygwin User Guide is well worth reading for some background on how Cygwin works.
6. Configure Cygwin for binary mode
$ mkdir /twiki /c c:/twiki $ mount -b -s c:/twiki /twiki $ mount -b -s c:/ /c $ mount -b -c /cygdrive $ mount Device Directory Type Flags C:\cygwin\bin /usr/bin system binmode C:\cygwin\lib /usr/lib system binmode C:\cygwin / system binmode c:\twiki /twiki system binmode c: /c system binmode
/twiki
(known as a 'mount point') to map onto c:/twiki
and for that directory tree to always be in binary mode, and does the same for /c
, mapping it onto c:/
. The last-but-one command sets binary as the default for any unmounted drives (e.g. z:/
, aka /cygdrive/z
).
mount
say 'binmode' under Flags
C:\cygwin
directories do not, you should uninstall and then re-install Cygwin to ensure that binary attachment uploads will work.
/twiki/bin/view
or /c/apache/Announcement
- see the Cygwin documentation for more details on this.
cd /twiki
echo hi >t
cat -v t
- you should see hi
as the output
hi^M
as output, your /twiki directory is not in binary mode
rm t
This setup is written to the Windows registry, so there's no need to put these commands into a .profile
file. For more information on binary vs text mode, see this User Guide section and this FAQ entry.
7. Download TWiki
Download the latest TWiki release (this cookbook is tested with the Dec 2001
release) from the URL that PeterThoeny sent you, and save it in the c:/twiki
directory.
8. Install TWiki
Unzip the ZIP file under c:/twiki
using WinZip, or by going into Cygwin and doing the following - you can hit the TAB
key to complete filenames after you've typed the first part:
$ cd /twiki $ unzip TWiki20011201.zip
Now that all the components are installed, you need to configure them.
The setup given here is fairly simple, in that it allows only TWiki to be served by the web server. For more complex setups, you can investigate the Alias and ScriptAlias commands that are left commented out in this configuration.
1. Configure Apache (part 1)
Using a suitable text editor (e.g. Cygwin's 'nano'
, or the Windows PFE editor, unless you already know 'vi'
), edit c:/apache/conf/httpd.conf
as follows - this tells Apache where TWiki lives, and removes the need to tinker with the Windows 2000 environment settings.
nano -w filename
- this turns off wrapping of long lines.
c:\temp
directory, by typing mkdir c:\temp
in a DOS command line window
# Change this to point to the Apache administrator (e.g. you) ServerAdmin you@yourdomain.com # Replaces DocumentRoot "C:/apache/htdocs" DocumentRoot "C:/twiki" # Replaces <Directory "C:/apache/htdocs"> <Directory "C:/twiki">
# Alias /twiki/ "C:/twiki/" # ScriptAlias /twiki/bin/ "C:/twiki/bin/" <Directory "C:/twiki/bin/"> # RD: Changed None to All in next line, to enable .htaccess AllowOverride All Allow From All Options ExecCGI SetHandler cgi-script </Directory> # Environment setup required to run Apache as service or as a # standalone process. <IfModule mod_env.c> # Adjust TZ for your server timezone, e.g. EST5EDT - put the non-daylight-savings # timezone code first (e.g. EST or GMT), followed by the number of hours that it's behind GMT # during non-daylight-savings time (use '-5' for timezones in advance of GMT). SetEnv TZ GMT0BST SetEnv RCSINIT -x,v/ # Adjust TEMP and TMP for your server and create directories if necessary SetEnv TEMP c:/temp SetEnv TMP c:/temp SetEnv LOGNAME system SetEnv HOME c:/twiki </IfModule>
2. Configure Apache (part 2)
Add an AddHandler line to the <IfModule mod_mime.c>
section of httpd.conf
- this removes the need to rename all the TWiki CGI scripts later in the installation.
# # Document types # <IfModule mod_mime.c> # TWiki setup - avoid renaming scripts AddHandler cgi-script . </IfModule>
3. Configure TWiki
Edit the TWiki config file, c:/twiki/lib/TWiki.cfg
(or in Cygwin terms, /twiki/lib/TWiki.cfg
) as follows:
c:/twiki
format pathnames for Cygwin, given the above binmode setup, but I have not tested this fully - a Cygwin Perl test script does generate binary mode files in this configuration, so it should work with RCS as well (really need a small RCS file corruption test case). Watch out for RCS file corruption carefully if you do try c:/twiki
pathnames with Cygwin, and do report your experiences...
fgrep
and egrep
to grep
, requiring the settings for these commands to point directly to grep
(with suitable flags to provide fgrep
and egrep
behaviour).
# variables that need to be changed when installing on a new server: # ================================================================== # http://your.domain.com/twiki : link of TWiki icon in upper left corner : $wikiHomeUrl = "http://yourdomain.com/bin/view"; # Host of TWiki URL : (Example "http://myhost.com:123") $defaultUrlHost = "http://yourdomain.com"; # /cgi-bin : cgi-bin path of TWiki URL: $scriptUrlPath = "/bin"; # /pub : Public data path of TWiki URL (root of attachments) : $pubUrlPath = "/pub"; # NOTE: Next three settings should be valid absolute pathnames using Cygwin; if using # TWiki:Codev.ActiveState Perl, use z:/twiki format pathnames if your TWiki directory is not on C:. # Public data directory, must match $pubUrlPath : $pubDir = "/twiki/pub"; # Template directory : $templateDir = "/twiki/templates"; # Data (topic files) root directory : $dataDir = "/twiki/data"; .... # Set ENV{'PATH'} explicitly for taint checks ( #!perl -T option ) : # (Note: PATH environment variable is not changed if set to "") # On Windows, $safeEnvPath needs only one component, the directory where RCS is installed # - used by 'rcsdiff' to run 'co' program, so PATH must be correct. # Unix/Linux setting: # $safeEnvPath = "/bin:/usr/bin"; # Using Cygwin perl, so can use Unix-like paths, with ':' as separator. # Note that /usr/bin and /bin are identical due to default /usr/bin mount # in Cygwin. Must NOT use 'c:/foo' type paths, as ':' is taken as separator # meaning that 'c' is interpreted as a pathname, giving Perl taint error. $safeEnvPath = "/bin"; # If using ActiveState perl, use Windows paths instead # $safeEnvPath = "c:/cygwin/bin"; ... # RCS directory (find out by 'which rcs') : $rcsDir = "c:/cygwin/bin"; ... # Unix egrep command : $egrepCmd = "/bin/grep -E"; # Unix fgrep command : $fgrepCmd = "/bin/grep -F";
For the cookbook install using Cygwin Perl, there's no more TWiki.cfg
editing to be done, so you can get onto the next section.
# NOTE: When using ActiveState Perl, you must specify # a full Windows-style pathname, using '\\' for backslashes, # for the ls, egrep and fgrep commands, because Cygwin's shell # is not used - forward slashes are OK in Windows everywhere # except in the cmd.exe shell. Drive letters are OK - e.g. # 'c:\\foo\\ls' will work. When using Cygwin perl, just # use the default '/bin/ls' type settings. # # Unix ls command : $lsCmd = "c:\\cygwin\\bin\\ls"; # Unix egrep command : $egrepCmd = "c:\\cygwin\\bin\\grep"; # Unix fgrep command : $fgrepCmd = "c:\\cygwin\\bin\\grep";
4. Editing the Shebang lines
Now to edit the curiously named 'shebang lines' at the top of the TWiki CGI scripts...
perl
line, you can restore from the .backup
directory and re-run the command, as it will only edit the original files, not the backups with '~' suffixes.
$ cd /twiki/bin $ ls attach geturl oops rdiff save testenv viewfile changes installpasswd passwd register search upload edit mailnotify preview rename statistics view $ mkdir .backup $ cp * .backup $ head -1 view #!/usr/bin/perl -wT $ perl -pi~ -e 's;#!/usr/bin/perl;#!c:/cygwin/bin/perl;' *[a-z] $ head -1 view #!c:/cygwin/bin/perl -wT $ ls attach geturl oops rdiff save testenv viewfile~ attach~ geturl~ oops~ rdiff~ save~ testenv~ view~ changes installpasswd passwd register search upload changes~ installpasswd~ passwd~ register~ search~ upload~ edit mailnotify preview rename statistics view edit~ mailnotify~ preview~ rename~ statistics~ viewfile
If for some reason the edit goes wrong, just type cp .backup/* .
(while within the bin
directory) to restore the original distribution files. Use ls -a
to see the .backup
directory, and ls -a .backup
to view its contents.
Optional step: you can do 'rm *~'
to clean out the backups made by Perl, but that's not essential as all the original files cannot be executed. If you do this, type the command very carefully, as a space after the '*' will wipe out all files in this directory!
5. Minor changes to TWiki scripts
As an interlude, you now need to make some minor edits to files in the c:/twiki/bin
directory, using a suitable editor (remember to use nano -w filename
if you prefer nano
to vi
- or just use the Windows PFE editor).
register
script in /twiki/bin
- change line 200 to read as follows (insert the MIME::Base64::
part):
return $user . ':{SHA}' . MIME::Base64::encode_base64(Digest::SHA1::sha1($passwd));
testenv
, see TWiki:Codev.CookbookActivePerlTestenv
6. Installing required Perl modules
Some additional Perl modules are needed for the register
script to work properly. Fortunately, there is an automated tool that makes it easy to do this - it's called cpan
, and goes to the Perl module archive site, http://www.cpan.org/, to download all required modules, and then build and install them. Here's what you need to do:
First of all, you need to get the cpan
tool configured and working - this is only necessary once. From the Cygwin shell, type the following (putting the export
command in ~/.profile
is recommended to make this setting persistent). Without the TEMP variable, some modules may fail to install on Windows 2000 and higher.
$ export TEMP=/c/temp $ cpan Lots of questions about configuration and preferences - just hit Enter until you get to the questions about mirror sites, but answer the questions about FTP proxies etc if you are behind a proxy-based firewall. The CPAN tool will fetch a series of files, some quite large, as part of this setup process, so be patient...
NOTE: If you are behind a non-proxy-based firewall that requires the use of passive FTP, the initial downloads of files using Net::FTP may appear to hang - just wait 5 or more minutes, however, and the CPAN tool should eventually hit on ncftpget
, which is part of Cygwin and does work OK. If this doesn't work and you are behind a typical NAT-based firewall, try doing the following at the Cygwin shell before running cpan
- this forces Net::FTP to use passive FTP, letting it get through such firewalls:
$ export FTP_PASSIVE=1If this works, add this line to your
~/.profile
file for future use.
Once some initial files are downloaded, you are asked to select your continent and country, and then mirror sites - just type the number of the mirror sites you want to use (pick a few in case one is down):
... (28) Turkey (29) Ukraine (30) United Kingdom Select your country (or several nearby countries) [] 30 (1) ftp://cpan.teleglobe.net/pub/CPAN (2) ftp://ftp.clockerz.net/pub/CPAN/ (3) ftp://ftp.demon.co.uk/pub/CPAN/ (4) ftp://ftp.flirble.org/pub/languages/perl/CPAN/ (5) ftp://ftp.mirror.ac.uk/sites/ftp.funet.fi/pub/languages/perl/CPAN/ (6) ftp://ftp.plig.org/pub/CPAN/ (7) ftp://mirror.uklinux.net/pub/CPAN/ (8) ftp://sunsite.doc.ic.ac.uk/packages/CPAN/ (9) ftp://usit.shef.ac.uk/pub/packages/CPAN/ Select as many URLs as you like, put them on one line, separated by blanks [] 4 7 8 Enter another URL or RETURN to quit: [] New set of picks: ftp://ftp.flirble.org/pub/languages/perl/CPAN/ ftp://mirror.uklinux.net/pub/CPAN/ ftp://sunsite.doc.ic.ac.uk/packages/CPAN/
Eventually, you'll get to the CPAN tool's shell prompt, where you need to install a few modules - the tool will do all the work for you.
make
and gcc
packages, which are required by the CPAN installer (gcc
is required for modules that include C language code) - you can install them now by launching Cygwin's setup.exe
from c:/download/cygwin-dist
(no need to exit the CPAN installer).
cpan shell -- CPAN exploration and modules installation (v1.59_54) cpan> install Net::SMTP May already be installed - if it is, try 'force install', since it's useful to be able to set firewall and passive FTP configuration when using Net::FTP. Make sure you answer 'Y' to the question about whether you want to configure this package. cpan> install Digest::SHA1 Lots of output about how CPAN finds, builds and installs the module - watch for any errors, though it should work fine if you have installed the Cygwin packages listed above (particularly 'gcc' and 'make'). cpan> install MIME::Base64 May already be installed.
7. Re-locking files
First, some testing: in your browser, go to http://yourdomain.com/bin/testenv - this provides a lot of detail, including warnings. Write down the Apache server's userid that is given by this script - typically either 'system' or 'administrator' - I'll assume 'system' from now on.
testenv
script doesn't work, go back and check the configuration of the Apache httpd.conf
file, and TWiki.cfg
. Have a look at the Apache error log, c:/apache/logs/error_log
, and the TWiki error log, /twiki/data/log*.txt
.
This 'system' user must own the locks on the RCS files, which are shipped with the lock held by 'nobody'. The reason this matters is that no revisions will be tracked by RCS unless the Apache userid matches that of the RCS file locks.
You can re-lock files using rcs -u
and rcs -l
, but it's a painfully manual process. Instead, just use Perl again to mass-edit all the RCS files, as follows:
$ cd /twiki/data $ : Make a backup of all files $ tar czvf all-files.tar.gz */* $ : Test edit a single file to check your typing $ perl -pi~~~ -e 'NR <= 10 && s/nobody:/system:/ ' Main/WebIndex.txt,v $ diff Main/WebIndex.txt,v Main/WebIndex.txt,v~~~ 5c5 < system:1.2; strict; --- > nobody:1.2; strict; $ : Now edit all the RCS files at once - use cursor-up to recall previous command $ perl -pi~~~ -e 'NR <= 10 && s/nobody:/system:/ ' */*,v $ : Check for any remaining files not edited $ grep 'strict;$' */*,v | grep -v system $ : Clean up - type this very carefully $ rm */*~~~
tar xzvf all-files.tar.gz
and all your files, both .txt and .txt,v, will be back as they were before the edits.
You have now re-locked all the RCS files and are ready to start using TWiki! Of course, testing that it works is always a good idea, so that's next.
8. Email setup for notification and registration
You need to set the SMTPMAILHOST
to an SMTP email host that is reachable and currently working. Otherwise you'll get a confusing message from TWiki when registering new users or running mailnotify
(for WebNotify), along the lines of:
Software Error: Can't call method "mail" on an undefined value at ../lib/TWiki/Net.pm line 187.
There are other settings to be made in TWikiPreferences, e.g. the WIKIWEBMASTER
and (probably) the SMTPSENDERHOST
(normally your mail server or TWiki server). See the TWikiInstallationGuide for more details, what's listed here is just enough to let you run the basic tests.
Do try and exercise your TWiki in test mode before you release it to other users or put any significant data into it.
Here are the main things to test:
http://yourdomain.com/bin/testenv
and check for warnings
view
script) - click around a few pages and make sure the links are OK
rdiff
script) - click on the Diffs link and on the '>' links at bottom of page
register
script to create a new user entry in /twiki/data/.htpasswd
(the Apache password file), ability to send email via Net::SMTP, and whether SMTPMAILHOST
was set correctly in TWikiPreferences.
tail -30 /c/apache/logs/error_log
to see last 30 errors from Apache
error_log
file to see if there are any RCS errors so far
ls
and grep
are working
ls
and grep
are working
/twiki/pub
directory.
error_log
file again
If anything doesn't work, go back and check the configuration of the Apache httpd.conf
file, and TWiki.cfg
. Have a look at the Apache error log, c:/apache/logs/error_log
, and the TWiki error log, /twiki/data/log*.txt
, and if necessary enable debugging on selected scripts (the commands are right at the top of each script) - the results go into /twiki/data/debug.txt
. There is also a /twiki/data/warning.txt
file that contains less serious messages.
See TWiki:Codev.TWikiPatches in case there are patches (i.e. specific code changes) for particular problems that may affect you (e.g. TWiki:Codev.ChangePasswordOnWin2K).
If you find that the Index feature doesn't work, or topic name searches fail, you should check you have set $egrepCmd
and $fgrepCmd
correctly, as mentioned above.
TWiki:Codev.CygWin has several models for how it does security:
#!/bin/something
). This is what has been used for this cookbook.
I have not had any problems with TWiki permissions on Windows, unlike Linux/Unix, which is probably because I'm using the default security model for Cygwin. If you use the other models, you may still be OK if you have local admin rights, and Apache is running as the SYSTEM user (which it uses if started as a service). If you do have trouble in this area, see the TWikiInstallationGuide's advice, some of which will apply to TWiki:Codev.CygWin, and log any issues in TWiki:Codev.WindowsInstallCookbookComments.
See the TWikiInstallationGuide for other setup. In particular, you'll probably want to refer to the section on basic authentication - remember to use c:/twiki
type filenames (i.e. Windows format) since you are using Apache for Windows.
You may want to investigate TWiki:Codev.WindowsInstallModNTLM, which describes how to add an Apache module so that TWiki:Codev.InternetExplorer users are automatically authenticated based on their Windows domain login - this avoids TWiki:Codev.GettingTheUsernameWrong and TWiki:Codev.ForgettingPasswords, which are usually very common among TWiki users.
See TWiki:Codev.WindowsModPerlInstallCookbook and TWiki:Codev.ModPerl for information on installing TWiki under Apache's mod_perl
- this is somewhat more complex and follows a different model, so it's best to get some experience with TWiki, Apache and Perl first.
In your TWiki on Windows installation, it's worth remembering that:
.htaccess
file and c:/apache/conf/httpd.conf
) always use Windows format paths, with forward slashes, e.g. c:/twiki
c:/cygwin/bin/perl
/twiki
(using Cygwin Perl as per this cookbook)
c:/twiki
/twiki
Material in this cookbook is heavily based on the enormous number of contributions in TWiki:Codev.TWikiOnWindowsArchive and related topics - too many people to thank, but have a look at the contributor list to TWiki:Codev.TWikiOnWindowsArchive to get an idea!
People who've tested or reviewed this document and provided valuable feedback include:
-- PeterThoeny - 30 Jan 2003
Topic WindowsInstallCookbook . { |
Revision r1.1 - 30 Jan 2003 - 09:17 - PeterThoeny |
Copyright © 1999-2025 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki.Tukro? Send feedback. |