text:
Apache HTTP Server Version 2.4
This document explains how to install, configure and run Apache 2.0 under Novell NetWare 6.0 and above. If you find any bugs, or wish to contribute in other ways, please use our bug reporting page.
The bug reporting page and dev-httpd mailing list are not provided to answer questions about configuration or running Apache. Before you submit a bug report or request, first consult this document, the Frequently Asked Questions page and the other relevant documentation topics. If you still have a question or problem, post it to the novell.devsup.webserver newsgroup, where many Apache users are more than willing to answer new and obscure questions about using Apache on NetWare.
Most of this document assumes that you are installing Apache from a binary distribution. If you want to compile Apache yourself (possibly to help with development, or to track down bugs), see the section on Compiling Apache for NetWare below.
Apache 2.0 is designed to run on NetWare 6.0 service pack 3 and above. If you are running a service pack less than SP3, you must install the latest NetWare Libraries for C (LibC).
NetWare service packs are available here.
Apache 2.0 for NetWare can also be run in a NetWare 5.1 environment as long as the latest service pack or the latest version of the NetWare Libraries for C (LibC) has been installed . WARNING: Apache 2.0 for NetWare has not been targeted for or tested in this environment.
Information on the latest version of Apache can be found on the Apache web server at http://www.apache.org/. This will list the current release, any more recent alpha or beta-test releases, together with details of mirror web and anonymous ftp sites. Binary builds of the latest releases of Apache 2.0 for NetWare can be downloaded from here.
There is no Apache install program for NetWare currently. If you are building Apache 2.0 for NetWare from source, you will need to copy the files over to the server manually.
Follow these steps to install Apache on NetWare from the
binary download (assuming you will install to
volume (may be installed to any volume)
apache2.conf file setting
ServerRoot and
ServerName along with any file path values
to reflect your correct server settings
SYS:/APACHE2 to the search path, for example:
Follow these steps to install Apache on NetWare manually
from your own build source (assuming you will install to
Apache2 on a
NetWare volume
HTTPD-STD.CONF file to the
SYS:/APACHE2/CONF directory and rename to
CHARSET.CONV and
MAGIC files to
SYS:/APACHE2/CONF directory
on the server
on the server
and copy all nlm modules into the
modules directory
HTTPD.CONF file searching for all
@@Value@@ markers and replacing them with the
appropriate setting
SYS:/APACHE2 to the search path, for example:
Apache may be installed to other volumes besides the default
SYS volume.
During the build process, adding the keyword "install" to the makefile command line
will automatically produce a complete distribution package under the subdirectory
DIST. Install Apache by simply copying the distribution that was produced
by the makfiles to the root of a NetWare volume (see: Compiling Apache for
NetWare below).
To start Apache just type
apache at the
console. This will load apache in the OS address space. If you
prefer to load Apache in a protected address space you may
specify the address space with the load statement as follows:
load address space = apache2 apache2
This will load Apache into an address space called apache2. Running multiple instances of Apache concurrently on NetWare is possible by loading each instance into its own protected address space.
After starting Apache, it will be listening to port 80
(unless you changed the
directive in the configuration files).
To connect to the server and access the default page,
launch a browser and enter the server's name or address. This
should respond with a welcome page, and a link to the Apache
manual. If nothing happens or you get an error, look in the
error_log file in the
Once your basic installation is working, you should
configure it properly by editing the files in the
conf directory.
To unload Apache running in the OS address space just type the following at the console:
unload apache2
apache2 shutdown
If apache is running in a protected address space specify the address space in the unload statement:
unload address space = apache2 apache2
When working with Apache it is important to know how it will find the configuration files. You can specify a configuration file on the command line in two ways:
-f specifies a path to a particular
configuration file
apache2 -f "vol:/my server/conf/my.conf"
apache -f test/test.conf
In these cases, the proper
should be set in the configuration file.
If you don't specify a configuration file name with
Apache will use the file name compiled into the server, usually
conf/apache2.conf. Invoking Apache with the
switch will display this value labeled as
Apache will then determine its
by trying the following, in this order:
ServerRoot directive via a
-C switch.
-d switch on the command line.
The server root compiled into the server is usually
invoking apache with the
-V switch will display this value labeled as
Apache 2.0 for NetWare includes a set of command line directives that can
be used to modify or display information about the running instance of the
web server. These directives are only available while Apache is running. Each
of these directives must be preceded by the keyword
By default these directives are issued against the instance of Apache running in the OS address space. To issue a directive against a specific instance running in a protected address space, include the -p parameter along with the name of the address space. For more information type "apache2 Help" on the command line.
Apache is configured by reading configuration files usually stored
in the
conf directory. These are the same as files used
to configure the Unix version, but there are a few different directives for
Apache on NetWare. See the Apache
documentation for all the available directives.
The main differences in Apache for NetWare are:
Because Apache for NetWare is multithreaded, it does not use a separate process for each request, as Apache does on some Unix implementations. Instead there are only threads running: a parent thread, and multiple child or worker threads which handle the requests.
Therefore the "process"-management directives are different:
MaxConnectionsPerChild -
Like the Unix directive, this controls how many connections
a worker thread will serve before exiting. The recommended default,
MaxConnectionsPerChild 0, causes the thread to continue servicing
request indefinitely. It is recommended on NetWare, unless there is some
specific reason, that this directive always remain set to
StartThreads -
This directive tells the server how many threads it should start initially.
The recommended default is
StartThreads 50.
MinSpareThreads -
This directive instructs the server to spawn additional worker threads
if the number of idle threads ever falls below this value. The recommended
default is
MinSpareThreads 10.
MaxSpareThreads -
This directive instructs the server to begin terminating worker threads
if the number of idle threads ever exceeds this value. The recommended
default is
MaxSpareThreads 100.
MaxThreads -
This directive limits the total number of work threads to a maximum
value. The recommended default is
ThreadsPerChild 250.
ThreadStackSize -
This directive tells the server what size of stack to use
for the individual worker thread. The recommended default
ThreadStackSize 65536.
The directives that accept filenames as arguments must use
NetWare filenames instead of Unix names. However, because Apache
uses Unix-style names internally, forward slashes must be used
rather than backslashes. It is recommended that all rooted file paths
begin with a volume name. If omitted, Apache will assume the
SYS: volume which may not be correct.
Apache for NetWare has the ability to load modules at
runtime, without recompiling the server. If Apache is
compiled normally, it will install a number of optional
modules in the
\Apache2\modules directory.
To activate these, or other modules, the
LoadModule directive
must be used. For example, to active the status module, use
the following:
LoadModule status_module modules/status.nlm
Information on creating loadable modules is also available.
CGIMapExtension -
This directive maps a CGI file extension to a script interpreter.
SecureListen -
Enables SSL encryption for a specified port.
NWSSLTrustedCerts -
Adds trusted certificates that are used to create secure connections to proxied servers.
NWSSLUpgradeable -
Allow a connection created on the specified address/port to be upgraded to an SSL connection.
Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once
Apache has been built, it can be installed to the root of any NetWare
volume. The default is the
sys:/Apache2 directory.
Before running the server you must fill out the
directory. Copy the file
HTTPD-STD.CONF from the distribution
conf directory and rename it to
Edit the
HTTPD.CONF file searching for all
markers and replacing them with the appropriate setting. Copy over
conf/magic and
conf/mime.types files as well.
Alternatively, a complete distribution can be built by including the keyword
install when invoking the makefiles.
The following development tools are required to build Apache 2.0 for NetWare:
NOVELLLIBC to the
location of the NetWare Libraries for C SDK, for example:
Set NOVELLLIBC=c:\novell\ndk\libc
METROWERKS to the
location where you installed the Metrowerks CodeWarrior compiler,
for example:
Set METROWERKS=C:\Program Files\Metrowerks\CodeWarrior
Files\Metrowerks\CodeWarrior, you don't need to set this.
LDAPSDK to the
location where you installed the LDAP Libraries for C, for example:
Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc
ZLIBSDK to the
location where you installed the source code for the ZLib Library,
for example:
Set ZLIBSDK=D:\NOVELL\zlib
PCRESDK to the location
where you installed the source code for the PCRE Library, for example:
Set PCRESDK=D:\NOVELL\pcre
AP_WORK to the full path of
httpd source code directory.
Set AP_WORK=D:\httpd-2.0.x
APR_WORK to the full path of
apr source code directory. Typically
but the APR project can be outside of the httpd directory structure.
Set APR_WORK=D:\apr-1.x.x
APU_WORK to the full path of
apr-util source code directory. Typically
but the APR-UTIL project can be outside of the httpd directory structure.
Set APU_WORK=D:\apr-util-1.x.x
gmake.exe) have been included in the system's
PATH environment variable.
\httpd-2.0 and build the prebuild utilities
by running "
gmake -f nwgnumakefile prebuild". This target will create
the directory
\httpd-2.0\nwprebuild and copy each of the utilities
to this location that are necessary to complete the following build steps.
\httpd-2.0\nwprebuild\GENCHARS.nlm and
\httpd-2.0\nwprebuild\DFTABLES.nlm to the
SYS: volume of a
NetWare server and run them using the following commands:
SYS:\genchars > sys:\test_char.h
SYS:\dftables sys:\chartables.c
test_char.h and
to the directory
\httpd-2.0\os\netware on the build machine.
\httpd-2.0 and build Apache by running
gmake -f nwgnumakefile". You can create a distribution directory by
adding an install parameter to the command, for example:
gmake -f nwgnumakefile install
gmake -f nwgnumakefile
Builds release versions of all of the
binaries and copies them to a
\release destination directory.
gmake -f nwgnumakefile DEBUG=1
Builds debug versions of all of the
binaries and copies them to a
\debug destination directory.
gmake -f nwgnumakefile install
Creates a complete Apache
distribution with binaries, docs and additional support files in a
\dist\Apache2 directory.
gmake -f nwgnumakefile prebuild
Builds all of the prebuild utilities
and copies them to the
\nwprebuild directory.
gmake -f nwgnumakefile installdev
Same as install but also creates a
\lib and
\include directory in the destination directory
and copies headers and import files.
gmake -f nwgnumakefile clean
Cleans all object files and binaries
from the
\release.o or
\debug.o build areas depending on whether
DEBUG has been defined.
gmake -f nwgnumakefile clobber_all
Same as clean and also deletes the distribution directory if it exists.
Set EXPERIMENTAL=1
Set USE_STDSOCKETS=1
By default Apache for NetWare uses the built-in module
mod_nw_ssl to provide SSL services. This module
simply enables the native SSL services implemented in NetWare OS
to handle all encryption for a given port. Alternatively, mod_ssl
can also be used in the same manner as on other platforms.
Before mod_ssl can be built for the NetWare platform, the OpenSSL libraries must be provided. This can be done through the following steps:
NetWare/set_env.bat and modify any
tools and utilities paths so that they correspond to your build
Netware\set_env netware-libc
Netware\build netware-libc
Netware\build netware-libc nw-nasm enable-mdc2 enable-md5
OSSLSDK to the full path to the root of the openssl
source code directory, and set WITH_MOD_SSL to 1.
Set OSSLSDK=d:\openssl-0.9.8x
Set WITH_MOD_SSL=1


text:
MOB Dresses - Tulipia
Toronto, Mississauga, Hamilton and Barrie
* The MOB Tulipia gowns shown here represent just samples of the selection available.
Best for Bride invites you to browse thoroughly the finest selection of different styles and colors of Tulipia MOB Collection. These dresses are stylish gowns you will want to wear again and again to any event or special occasion. Whether you are looking for for a Formal Bridal gown, Bridesmaids dresses, Mother of the Bride / Mother of the Groom gowns or Prom dress, Tulipia's unique collection is for you! Enjoy this stunning, ultra-modern collection which features beautiful designs, luxurious fabrics and finest quality.
The Mother of the Bride dress manual
- Factors to consider when choosing the Mother-of-the-Bride dress
- How to find a flattering dress for the mother of the bride
- Know the best silhouettes for your body type
- Find colors that look best on you
- Choose a comfortable length
- Consider the neckline and sleeves

subset: commoncrawl


text:
Nicki Minaj Announces North American 'Pink Friday' Tour Dates
Nicki Minaj is painting the town pink. After opening for Lil Wayne and Britney Spears last year, hip-hop's reigning queen will headline her first tour in North America this summer.
The month-long "Pink Friday" trek will kick off July 16 in Chicago, traveling to Detroit, Atlanta, Miami, Houston, and Seattle, currently wrapping August 12 in Vancouver. Tickets for the Live Nation-produced event go on sale starting Friday, May 4.
In addition to her solo dates, the "Starships" rapper will play several radio shows including Wild 94.9s Wild Jam in San Francisco on May 10, 102.7 KIIS FM's Wango Tango in L.A. on May 12, Wired 96.5 Fest in Philadelphia on June 1, Jam'n 94.5 Summer Jam in Boston on June 2, Hot 97 Summer Jam in New York on June 3, and Hot Jam in Hartford on July 20.
Nicki will also bring back her intimate meet and greets. Fans will have the opportunity to purchase a VIP laminate and lithograph and be the first to enter the venue on the night of the show. During each meet and greet, Minaj will sign autographs and take photos with her Barbz. VIP packages will be available at www.mypinkfriday.com.
Before bringing her tour stateside, the hip-hop diva will tour Europe beginning June 8 in Stockholm, Sweden. Dates for her international shows in the U.K., Japan, and Australia sold out within hours.
"Pink Friday" North American Tour Dates
July 16 – Chicago, IL – The Chicago Theatre
July 17 – Detroit, MI – Fox Theatre Detroit
July 19 – Cleveland, OH – State Theatre at Playhouse Square
July 21 – Washington, D.C. – Constitution Hall
July 22 – Atlanta, GA – Fox Theatre Atlanta
July 24 – Miami, FL – James L. Knight Center
July 26 – Birmingham, AL – Boutwell Auditorium
July 27 – New Orleans, LA – Lakefront Arena
July 28 – Houston, TX – Bayou Music Center
July 29 – Dallas, TX – Verizon Theatre at Grand Prairie
July 31 – St. Louis, MO – Peabody Opera House
August 2 – Denver, CO – Wells Fargo Theatre
August 4 – Las Vegas, NV – Planet Hollywood Resort & Casino
August 5 – Los Angeles, CA – Nokia Theatre
August 7 – Phoenix, AZ – Comerica Theatre
August 9 – Oakland, CA – Paramount Theatre
August 11 – Seattle, WA – Paramount Theatre
August 12 – Vancouver, BC – Queen Elizabeth Theatre


text:
Need to contact us for any reason? Then use the form below to send us an email, and don't forget to leave your contact details so we can reply!
About Cookies
Cookies and AboutMyArea
AboutMyArea use cookies to enable some advanced functionality, including those used by 3rd parties such as Google Analytics and AddThis. Some pages may have other 3rd party "widgets" that utilise their own cookies. Please view the link below for help on managing these and other cookies.
By continuing to use our site, we will assume you're happy to accept our use of cookies.


text:
Non-motoring for sale in Gwynedd
Sorry, PistonHeads couldn't find any non-motoring for sale in Gwynedd.
- Anglesey
- Blaenau Gwent
- Borough of Newport
- Borough of Wrexham
- Bridgend
- Bridgend County Borough
- Caerphilly
- Carmarthenshire
- Ceredigion
- City of Cardiff
- Conwy
- Denbighshire
- Flintshire
- Gwynedd
- Merthyr Tydfil County Borough
- Monmouthshire
- Neath Port Talbot
- Pembrokeshire
- Powys
- Rhondda Cynon Taff
- Swansea
- Torfaen
- Vale of Glamorgan
No adverts found
We couldn't find any items to match your chosen search. We suggest refining your search criteria accordingly, or why not save your search and set up an alert for us to tell you when we have something suitable.


text:
Empress Of Canada party venue Picture #73 - Sunday August 21st, 2022
Seventy-third picture from 459 total
A Clubcatcher team member took picture 73 from Empress Of Canada party venue on Sunday August 21st. Check the amazing photograph to determine if we caught the best moment. Use the arrows or block numbers below the large photograph to navigate between pictures or visit the gallery for small thumbnails in a grid. The current photograph number appears inside a dark box directly underneath the large photograph.
Find out below if you have been CAUGHT!
party venue Gallery Photo SelectionView Empress Of Canada picture #72View Empress Of Canada picture #74
View Empress Of Canada Aug 21st, 2022 gallery
Try the photo collage editor to produce amazing effects!
See Empress Of Canada party venue images normal sized. ***
Picture not perfect? See the photographer recommended size of all photos on this website. Simply select disable auto-format button below. Horizontal scrolling may be necessary to view it in full size if you disable auto-format.
Order a print for $2.50 CDN*
This Picture at this party venue is available to order as a print at low prices. We produce them in our in-house photography studio.
Select the Online Orders tab above to learn more.
Download photo to computer! **
Download this photo from this party venue to your computer in original size in highest quality for FREE.
Should we remove the photo?
Does the garbage seem like a more apppropriate place for this particular image in this party venue? Make a request for us to remove it.
Make a photo collage! ***
This picture from the party venue Empress Of Canada is a great addition to your photo collage. Apply effects including scaling, greyscale, and more. Magic begins with a click of the button below.
Star in an image at any party venue!
This handy list briefly outlines all the steps necessary to make yourself stand out from the crowd and appear in a image online at Empress Of Canada and any other party venue:
- Be nineteen years of age or older.
- Select a good fashion style.
- Gather any necessary travel documents.
- Make that picture-perfect moment happen and have FUN!
Select any step above to learn more about it.
Tip number seven
Book a hotel if the party city is far
* Prices for prints are expressed in canadian dollars and excludes the shipping fee. The online shopping cart will then contain the images ordered. We recommend reviewing them before processing the order with paypal.
** Dimension is 1500 x 1000 pixels and file is a high-quality image file in JPEG format that requires 446 KB of disk space.
*** The picture Auto format and photo collage features require cookies to be enabled in your browser.


text:
Prices incl. VAT plus shipping costs
In stock, Delivery time appr. 2-5 workdays
In stock: 38
- Order number: 41764
- EAN Code 8713647417644
- EAN-13 Code 8714993851281
Superstar Aqua Face & Bodypaint 45 gram Carmine Red colour 139-85.128
This very user-friendly water Face Body paint is of very good quality. The colors are pretty bright, the facepaint works well and is good to remove. A thin layer of Superstar bodypaint is enough to set a beautiful covering base. The facepaint dries up quickly and does not turn off.
The matte colors are ideal for shrinking the base and putting lines. Because the shiny shimmer shimmer are a bit softer, they are very suitable for shrinking the base of your creations.
Working method
Superstar water face & body paint can be used with sponge and brush. If you use a brush make it wet and activate the facepaint just as you would with watercolor. For the use of the facepaint with a sponge you have 2 options. You can wet and squeeze the sponge after which you squeeze the sponge over the bodypaint to load it or use a spray bottle to wet the facepaint and then work with a dry sponge on the bodypaint.
Removing the facepaint of the face goes well with water and soap, but you can also use baby lotion wipes or makeup remover wipes / lotions. For any reason, do not remove the bodypaint! By boning the skin is irritated and that does not feel comfortable.
|45 g
|Face paint, Make-up
|Ingredients list:
|Glycerin, Colophonium, Polysorbate 20, PEG-75 Lanolin, Aqua, Kaolin, Talc, Zinc Stearate, Magnesium Aluminium Silicate, Calcium Carbonate, Sodium Hydroxymethylglycinate, CI 15850, CI 19140, CI 77120
|European Cosmetics Legislation:


text:
"As I am Independent Development sector professional, i have felt disparity between men and women wages, though work doubly hard to prove oneself."
Tag: BCGE
Recommended Reads
Good Guys
Good Guys is the first practical, research-based guide for how to be a male ally to women in the workplace. Filled with firsthand accounts from bothMORE
90s Bitch
To understand how we got here, we have to rewind the VHS tape. 90s Bitch tells the real story of women and girls in the 1990s, exploring how they wereMORE
Equal Power
As Minister for Women and Equalities in the coalition government, Jo Swinson learned the hard way that gender imbalance was the most intractable andMORE
No Difference between us
Explore with the children in your care the important issues of gender equality and respectful relationships. Combining cheerful illustrations and aMORE
Hood Feminism
Today's feminist movement has a glaring blind spot, and paradoxically, it is women. Mainstream feminists rarely talk about meeting basic needs as aMORE


text:
Page title
Search SAMHSA Publications and Digital Products
Store Facets Summary
Main page content
Permanent Supportive Housing Evidence-Based Practices (EBP KIT)
Published: July 2010This toolkit outlines the essential components for supportive housing services and programs for people living with mental illness disorders. It discusses how to develop and integrate evidence-based programs in mental health systems. The toolkit includes eight booklets on program development.
Integrated Treatment for Co-Occurring Disorders Evidence-Based Practices (EBP) KIT
Assertive Community Treatment (ACT) Evidence-Based Practices (EBP) KIT
Published: October 2008This toolkit offers tools to implement the evidence-based practice of Assertive Community Treatment (ACT). ACT offers customized, community-based services for people living with mental illness. The toolkit includes a brochure (English, Spanish), a PowerPoint presentation, and an introductory video.


text:
Difference between revisions of "User:Apizer/My sandbox"
|Line 1:
|Line 1:
Title: Installation Manual for 2.4.9 on Ubuntu 10.04LTS
<!-- {{UnderConstruction}} -->
<!-- {{UnderConstruction}} -->
These instructions cover the installation of the Ubuntu Linux 10.04 LTS operating system and WeBWorK 2.4 from scratch. Note that you can also quickly install Ubuntu 10.04 and WeBWorK 2.4 from the WeBWorK Live DVD (see [[Installing from WW2.4_Ubuntu9.10_Vanilla_LiveDVD]]).
These instructions cover the installation of the Ubuntu Linux 10.04 LTS operating system and WeBWorK 2.4 from scratch. Note that you can also quickly install Ubuntu 10.04 and WeBWorK 2.4 from the WeBWorK Live DVD (see [[Installing from WW2.4_Ubuntu9.10_Vanilla_LiveDVD]]).
Revision as of 08:33, 3 June 2011
These instructions cover the installation of the Ubuntu Linux 10.04 LTS operating system and WeBWorK 2.4 from scratch. Note that you can also quickly install Ubuntu 10.04 and WeBWorK 2.4 from the WeBWorK Live DVD (see Installing from WW2.4_Ubuntu9.10_Vanilla_LiveDVD).
If you are just upgrading WeBWorK, especially if you already have existing WeBWorK courses, see Upgrading WeBWorK.
These instructions are more detailed (but offer fewer choices and often less background information) than the general Installation Manual for 2.4 and are aimed at non unix experts. Readers may want to quickly scan Installation Manual for 2.4 to get an overview of the installation process and then carefully read and follow these instructions.
- 1 Notation
- 2 Installing the Ubuntu 10.04 Linux Operating System
- 3 Terminal Window Notation and Use
- 4 Ubuntu Software Packages
- 5 Installing Perl Modules
- 6 Apache 2 and mod_perl
- 7 Checking MySQL
- 8 Reboot and Test
- 9 Downloading the WeBWorK System Software and Problem Libraries
- 10 Installing WeBWorK
- 11 Configuring the Shell
- 12 Checking Module Dependancies
- 13 Configuring WeBWorK
- 14 Configuring Apache
- 15 Test your configuration
- 16 If Something is Wrong
- 17 Create the admin Course
- 18 Starting and Stopping Apache, MySQL and the GNOME desktop GUI
- 19 Install the WeBWorK Problem Libraries
- 20 Create Your First Actual Course
- 21 Test that Things are Working Properly
- 22 Optional Configurations
- 23 Updating WeBWorK files
- 24 Where to go From Here
First some short comments on notation we will be using. We will use
<key> to indicate that you should press a specific key (e.g.
<F12>, etc.). Sometimes we will also use e.g.
<root password> to indicate you have to enter the root password.
^ will indicate the
<Ctrl> key so e.g.
^X is really shorthand for
<Ctrl> <X>, i.e. press the Ctrl key and hit the X key.
We will give references to specific versions of software, e.g. httpd-2.2.4.tar.gz rather than the more general httpd-2.x.x.tar.gz. In most cases you should be able to use the latest stable version but we have only tested the versions listed.
Installing the Ubuntu 10.04 Linux Operating System
Installation CD
Obtain the
Desktop Edition installation DVD/CD set. Connect to http://www.ubuntu.com/ for information. For example you can use wxDownload Fast or BitTorrent to download an ISO image of the installation CD and then burn your own installation CD. You want the file
ubuntu-10.04.2-desktop-amd64.iso or, if you have a very old server,
ubuntu-10.04.2-desktop-i386.iso. Choose the former to take full advantage of computers based on the AMD64 or EM64T architecture (e.g., Athlon64, Opteron, EM64T Xeon, Core 2). Choose which ever download site works best for you; I have had good luck with http://mirrors.kernel.org/ubuntu-releases/ If you download the ISO image, make sure that you verify the integrity of the downloaded file by comparing the MD5 checksum of the downloaded file with the MD5 checksum listed at https://help.ubuntu.com/community/UbuntuHashes or at the download site (e.g. http://mirrors.kernel.org/ubuntu-releases/10.04/MD5SUMS). wxDownload Fast automatically calculates the MD5 checksums which is convenient. These instructions will assume you have the
ubuntu-10.04.2-desktop-amd64.iso installation CD but installing from the i386, alternate CD, a commercial DVD/CD set or from the net should be essentially identical.
You will want to have you computer connected by ethernet to the internet for the installation. Place the installation CD in your DVD/CD drive and reboot your computer from the DVD drive. You may have to press
<F12> during the boot process to bring up a boot menu which will allow you to select booting from the DVD. Or you many have to edit the BIOS to select the DVD as the first boot device.
After the system boots you will be presented with a series of 7 steps.
- Step 1
- On the first install panel keep English as the selected language and click
Install Ubuntu 10.04.2 LTS, the second option.
- Step 2
- Select a city in your time zone and hit
- Step 3
- Hit
Forwardto accept the default keyboard layout
Optional Configurations
If you will have a large number of users (say over a 1,000) and/or a slow server, you may want to consider the first two optimizations. They are independent but related and deal with how WeBWorK handles various temporary and static files. We call these two options Optional A and Optional B. The third option, Optional C, gives greater security.
Optional A creates a separate partition on which are stored all of WeBWorK's "temporary" files. These are mostly small files such as png images of equations, pdf files, etc that may be reused but if they are not present (e.g. if they get deleted) they will be seamlessly regenerated on the fly. There is no reason to back up such files and having them in a separate partition means that it is easier and faster to back up other partitions and skip backing up unnecessary files.
Optional B installs and configures a lightweight webserver. Apache is a very standard and powerful webserver which we use to serve WeBWorK pages. However its child processes use a lot of resources (e.g. memory). When serving static files and images, a much lighter weight webserver can be used. This can substantially reduce the load on a heavily used server.
Optional C configures Apache so that access to WeBWorK will be through an encrypted Secure Sockets Layer (SSL) with an https: URL.
Except for creating a separate partition, we will wait until WeBWorK is installed and tested before implementing these options. We mention them here because the next step is partitioning the disks.
Partition disks
- Step 4
- Next comes the
Partition diskspages. You should be able to accept the defaults unless you want to follow Optional A and/or create separate partitions for various directories. There is a lot of information on the web if you don't want to accept the default partition set up. If you want to implement Optional A follow the directions below.
Optional A: The default partitioning scheme creates just two partitions, a root (
/) partition and a swap partition. Here we will create those and an additional partition for WeBWorK's temporary files.
- On the
Partition diskspage use
<Tab>to select
Go Backand then select
Partition disks
- Use the down arrow to select your disk (
- On the
You have selected an entire device to partition...page select
Yesto the question
Create new empty partition table on this device
- On the
This is an overview...page select
- On the
How to use this free spacepage select
Create a new partition
- Now you have to decide how to allocate your disk space. The rule of thumb is to use twice the amount of RAM you have for swap (e.g. 2 GB if you have 1 GB of RAM). For WeBWorK's temporary files 25 GB for every 1,000 students should be ample. You can allocate the remainder of your disk space to the root (
/) partition. Actually if you are going through the trouble of doing this, you probably will want to research other partitioning recommendations.
- On the
The maximum size you can use...page enter the size for your root (
/) partition and
- Select
Primaryfor the type of the new partition
- Select
Beginningfor the location of the new partition
- Select
/for the Mount point of the new partition and then select
Done setting up the partition
Now we repeat the process for the partition which will hold WeBWorK's temporary files.
- On the
This is an overview...page select
- On the
How to use this free spacepage select
Create a new partition
- On the
The maximum size you can use...page enter the size for WeBWorK's temporary files partition. As we said 25 GB for every 1,000 students should be ample. Then
- Select
Logicalfor the type of the new partition
- Select
Beginningfor the location of the new partition
- Select
Mount pointand then hit
- Select
Enter manuallyand then hit
- For the
Mount point for this partitionenter
- Then select
Done setting up the partition
Finally we set up the swap partition
- On the
This is an overview...page select
- On the
How to use this free spacepage select
Create a new partition
- On the
The maximum size you can use...page enter the size for swap partition. As we said the rule of thumb is to use twice the amount of RAM you have. Then
- Select
Logicalfor the type of the new partition
- Select
Beginningfor the location of the new partition
- Select
Use asand then hit
- Select
swap areaand then hit
- Then select
Done setting up the partition
- Review your changes and
- Select
Finish partitioning and write changes to diskand then hit
- Select
Yesto confirm the changes
Continue Initial Installaion
- Step 5
- The next panel asks "What is your name?". What you fill in here is a privileged user so you might want to enter a special administrative account rather than your normal account.
- Enter the information for "What is your name?"
- Enter the information for "What name do you want to use to log in?"
- Enter the information twice for the password
- Enter the information for the name of the computer
- Then hit
Forwardto continue
- Step 6
- If the
Migrate Documents and Settingspage appears just hit
Forwardto continue without importing anything
- Step 7
- Finally hit
Installon the Ready to install page to begin the installation. The
Advanced...button on this page gives you options on installing the boot loader but you almost certainly want to use the defaults.
Now sit back and relax while the installation takes place. Some of the steps can take a long time. Please be patient. When you finally see "Installation complete" hit
Restart now.
Continue Installation
After this finishes the system will eject the CD and ask you to reboot.
- Log into your account
- At some point the
Update Managerwindow may pop up. If it does, accept all updates. Alternately you can select
Update Manager. Click
install Updates. You may have to enter the
<wwadmin password>which functions as the
<root password>. Follow any instructions, e.g. you may be told to reboot as soon as the installation is completed (to reboot, click on your name in the upper right hand corner, then select
Test Browser and Keyboard
After reboot and login, click on
Firefox Web Browser (or just click the Firefox icon at the top of the screen) and you should be connected to the world.
where you can view this document and, if you want, copy commands that you need (see below).
If something is wrong and you are not connected to the web, the first thing to do is check that you entered the correct network information.
- Select
Network Connections
- Select
Auto ethoand click
- Select
IPv4 Settings
- Check that all the entries are correct and edit them if they are not
- If you change something click
- Enter
<wwadmin password>and click
- Click on
Closeto close
Network settings
Your network connection should start up almost immediately. If you are still having problems first try rebooting and if that doesn't work it's time to investigate further or seek help.
Here's an aside on keystroke delay and repetition rate. If you are like me and find the keystroke delay too short (so that you often type "geeet" when you want to type "get"), do the following. Click
Keyboard and then increase the delay time interval and hit
Terminal Window Notation and Use
Before installing and configuring additional software, we need to talk about terminal windows.
To open a terminal window click
Accessories and then select
In a terminal window some commands will have to be run as root whereas others should be run as a regular user. We will use # to indicate that the command is to be run as root e.g.
# perl -MCPAN -e shell
and $ to indicate that the command is to be run as a normal user e.g.
$ cp .bashrc .bashrc.bak1
To execute the above commands you have to hit
<Enter>. We'll just assume this.
After executing a command, often the system will respond with text (sometimes a lot of text!) which we will usually not repeat below. We only give the commands that you should execute.
The bash shell which you will be using has a number of very convenient features.
One is command and file name completion. If you are typing (e.g.
ch) and hit
<tab> bash will complete the command or filename if it is
unambiguous (or more precisely it will complete as much as possible).
If there are multiple possibilities (as in the case of
ch) nothing will
happen (except you may hear a beep) and you can type more letter(s) and hit
<tab> again. Or you can
<tab> a second time and you will see a list of all possible
completions. E.g. entering
ch<tab><tab> gives a list of possible
completions and
ch<tab>g<tab> (or
chg<tab>) gives
chgrp, the change group command. This
is very fast and convenient and it also leads to fewer typing errors.
Another useful shortcut is the command history. Using the up and down arrow keys will bring up previous commands which can be edited and then executed. If you are repeating a command or entering a command which is similar to a previous one, this is very useful.
You can copy commands from these instructions (with
copy from the Edit dropdown list or
^C) and paste them into a terminal window
paste from the Edit dropdown list or
<Shift> <Ctrl> <V>). This is an excellent way to use these instructions since it is fast and insures commands are entered correctly (just be careful to read before you run the command and replace things like
database_password with the correct code in the few places such things occur).
By default Ubuntu has no password set for the root user. To gain root access you have to use the
sudo command with the
<wwadmin password>. This is the password you set for the first user (which we called the WeBWorK administrator
<wwadmin> while installing Ubuntu. However we will
manually set a password for the root user since this is a much more standard setup. To do this, type in the following in a terminal window:
$ sudo passwd Password: <wwadmin password>
After that you are asked to type in the new root password twice. Enter the password for the root user and Do not forget what you enter here.
Enter new UNIX password: <root password> Retype new UNIX password: <root password> passwd: Password updated successfully $
To test this
$ su Password: <root password> # whoami root # exit $
Finally perhaps a safer way to run commands as
root is to use the
sudo command
$ sudo <command> Password: <wwadmin password>
After you enter the password the command is executed. For a certain period (maybe 5 minutes) you can execute additional
sudo commands without reentering
<wwadmin password>. A log of all
sudo commands is kept in
/var/log/auth.log . In these instructions for the most part we will not use
sudo, but keep it in mind for other times that you have to become
root in order to execute a few commands (e.g. restarting
Note that for certain GUI tools such as the
Synaptic Package Manager that require root access, the password required is
<wwadmin password>, the password for the first account you set up, not the new
<root password>.
For our next terminal window task create a
downloads directory where we will keep copies of downloaded software.
$ cd $ mkdir downloads
Ubuntu Software Packages
Our next task is to install a number of Ubuntu software packages. For a very fast way to do this, copy the command at the end of this section, paste it into a terminal window and run it as root. Or you can go through the step by step process using the
Synaptic Package Manager as follows.
- Select
Administrationand then
Synaptic Package Manager. You will have to enter the
<wwadmin password>. The
Synaptic Package Managerwindow will open
- Click on
Reloadto bring the package information up to date
Now we will actually select and install a large number of packages. The process is the same for all packages. I'll give an example of installing
libnet-ldap-perl and then just give the list of required packages.
- Select
- Under
Look in:select
Name. The default
Description and Namesometimes returns too many possibilities
- We are searching for
libnet-ldap-perlso enter
ldap-perl(or something similar; you can copy and paste from this document if you want) and click on
- This should result in 6 possibilities. Select and Mark for Installation (by double clicking or checking and then selecting
Mark for Installation)
libnet-ldap-perl. You will see a pop up window
Mark additional required changes?and you should always click
Markto accept the requirements.
- Follow this basic procedure for all the packages listed below
Here is the list of Ubuntu packages that need to be installed. See Installation Manual for 2.4 for a short explanation of what most of these packages do.
When I do this I see on the bottom of
Synaptic Package Manager window
82 to install/upgrade,
1 to remove. Your numbers may differ slightly.
Now click
Apply and
Apply again to confirm the changes. You will be asked to enter a
New password for the MySQL "root" user. Enter your choosen MySQL
root password. As was said above, Do not forget what you enter here. Also remember that this is the password for the MySQL
root user, not the Ubuntu linux system
root user. Below we refer to this as
<mysql root password>
That completes the set up of your base Ubuntu system. You can quit the
Synaptic Package Manager.
If you would prefer to install all of these packages in one fell swoop, run the following command as root (
$ su <Enter> ;
Password: <root password> ):
# aptitude install apache2 apache2-mpm-prefork dvipng gcc libapache2-request-perl libdatetime-perl libdbd-mysql-perl libemail-address-perl libexception-class-perl libextutils-xsbuilder-perl libgd-gd2-perl libmail-sender-perl libmime-perl libnet-ip-perl libnet-ldap-perl libossp-uuid-perl libpadwalker-perl libphp-serialization-perl libsoap-lite-perl libsql-abstract-perl libstring-shellquote-perl libtimedate-perl libxml-parser-perl libxml-writer-perl make mysql-server netpbm openssh-server preview-latex-style subversion texlive unzip
When prompted, you can always accept the default (hit
<Enter>) except when asked for the password for the MySQL "root" user. In case you skipped by it, look above for information on the
New password for the MySQL "root" user. When the process finishes, enter
# exit
to return to a regular user.
Installing Perl Modules
We now have to install several additional Perl modules which unfortunately are not available from the Debian package system.
Testing Perl Modules
To test if a Perl module is installed and working on your system, issue the following command, replacing
Module with the name of the module:
$ perl -MModule -e 'print "installed!\n"'
If the module is installed you will see
installed!. If not you will see at lot of gibberish. E.g. at this stage in our installation process
CPAN is installed and
MXML::Parser::EasyTree is not so
$ perl -MCPAN -e 'print "installed!\n"'
$ perl -MXML::Parser::EasyTree -e 'print "installed!\n"'
Can't locate XML/Parser/EasyTree.pm in @INC (@INC contains: /etc/perl ...
You can check the version of an installed module by the following command, replacing
Module with the name of the module:
perl -MModule -e 'print "$Module::VERSION\n"'
For example for the GD.pm module
perl -MGD -e 'print "$GD::VERSION\n"'
Installing Additional Perl Modules from CPAN
Be aware that in rare cases you might have to as root run
$ su <root password> # unset LANG # exit $
since otherwise the installation of some modules (Module::Build is an example) may fail.
First we will set up CPAN. For this you have to be root.
$ su <root password> # perl -MCPAN -e shell
Since this is the first time you are using CPAN it will ask you
Would you like me to configure as much as possible automatically?
Yes and that should be it.
Next we add at least one mirror and reload the index. A list of mirrors can be found at http://mirrors.cpan.org. I have had good luck with the mirror ftp://mirrors.kernel.org/pub/CPAN .
To add the mirror ftp://mirrors.kernel.org/pub/CPAN and reload the index do the following. For me, a slow and inaccurate typist, copying (
^C) and pasting (
<Shift> <Ctrl> <V>) is much faster.
cpan> o conf urllist push ftp://mirrors.kernel.org/pub/CPAN cpan> reload index
Note that one time this failed when I tried to do it in the evening but when I tried again the next morning it worked fine. Now we update CPAN itself
cpan> install Bundle::CPAN
and always hit
<Enter> to accept the defaults when prompted. This can be a long process with many long pauses. Please be patient.
When you again see the
prompt enter
cpan> reload cpan cpan> o conf commit
Now install the following modules
cpan> install XML::Parser::EasyTree Iterator Iterator::Util Pod::WSDL
and in case you are prompted accept all defaults by just hitting
Note that with more than one module to install, we just list them after
install separated by spaces.
When you again see the
prompt enter
cpan> exit #
Installing Additional Perl Modules from Source
At one point in time (August 2006), the installation of
DateTime using CPAN was broken. Currently
DateTime can be installed using CPAN. However it is useful to show you how to install perl modules from source in case one of the perl modules we installed above gets updated and its installation from CPAN becomes broken. If that happens you can follow the procedures outlined here to install the module from source.
IMPORTANT: With Ububtu we have already installed
DateTime so you don't have to install it as outlined below. We are just using this as an example of installing a module from source which hopefully you will never have to do. You can skip this section and go directly to the Apache 2 and mod_perl section.
Now we give the example of installing
DateTime from source. As we said you can skip this part.
Goto http://search.cpan.org/,
search for
DateTime and click on
DateTime. Then near the top right download
DateTime-0.36.tar.gz and save it to disk. Move it to your
downloads directory. Then
$ cd $ cd downloads $ tar -zvxf DateTime-0.36.tar.gz $ cd DateTime-0.36/ $ perl Makefile.PL $ make $ make test
make test indicates something is missing you will have to install that. In fact in the case of
DateTime, you would see that quite a few things are missing.
DateTimerequires the additional modules
DateTime::Locale. We could install these using CPAN
# perl -MCPAN -e shell cpan> install version Module::Build Class::Singleton DateTime::TimeZone DateTime::Locale cpan> exit # exit $
If you see anything that looks suspicious during this process, you can always test to see if the perl module in question was in fact installed. If it was not installed
try CPAN first and if CPAN fails then install it from source. The great thing about CPAN (if it works) is that it will trace down and automatically install all required components. Note that if you get a message indicating that
package/file.pm was not found, you should serach for and install
package::file since perl modules use a double colon (
::) as a directory separator.
Assuming all is OK
$su <root password> # make install # exit $
Finally you should definitely test that the module (e.g.
DateTime) was installed sucessfully
$ perl -MDateTime -e 'print "installed!\n"'
If you see
you can celebrate.
Apache 2 and mod_perl
First we have to enable a couple Apache modules. Acting as
root in a terminal window enter
# a2enmod apreq # a2enmod info
Next we make a copy of the configuration files for safekeeping.
# cd /etc/apache2/mods-available # cp info.conf info.conf.bak1 # cp status.conf status.conf.bak1
Now we will edit configuration files
info.conf and
status.conf to allow us to view information about the setup and performance of the web server. Note that this is not absolutely necessary but it can be very useful. You can use your favorite editor but we will give instructions assuming you are using
gedit. Note that you have to be root to edit these files. First we edit
# cd /etc/apache2/mods-available # gedit info.conf
You will see a lot a warning messages since Ubuntu doesn't like you to run gedit as root. You can ignore these or use sudo instead.
I suggest you allow access to server information from e.g. your department domain. To do this uncomment (i.e. remove the
# from)
# Allow from .example.com
and then replace
.example.com by
where of course you should edit
.math.yourschool.edu appropriately.
Then save the file and quit (
Save and
Now we edit
# cd /etc/apache2/mods-available # gedit status.conf
After the comments at the top and above the
<Location /server-status> line enter
ExtendedStatus On
Now edit the
# Allow from .example.com
line just as you did for
Then save the file and quit
Now we have to set your server's fully qualified domain name. Note that if your network was set up automatically via DHCP, your server's fully qualified domain name should already be set up. You can check by running the
hostname commands below.
First we have to install the network manager since it is no longer installed by default in Ubuntu. You can use the Synaptic Package Manager to install
gnome-network-admin but the quickest way is to run the command
$sudo apt-get install gnome-network-admin
After this is installed
- Select
- Click on
Click to make changes
- Enter
<wwadmin password>and click
- Click on
- Under
Host nameenter
your_server_name(if it's not already there)
- Then under
Domain nameenter your server's domain name, something like
- Click on
- There should also be an entry with your server's IP address (if not you should add one)
- Select the entry with your server's IP address and click
Properties(NOTE: with 9.04 clicking
Propertiesclosed the window. In order to edit an entry I first had to delete and then add it back as a new entry. So here and below you may have to use that method to for editing)
- Under Aliases you should see your server's fully qualified domain name, something like
- Add or edit these entries if they are not correct
- Then click
- And click
Closeto close
Network settings
You can check these settings by running the commands
$ hostname --fqdn
$ hostname
The first respond with the fully qualified domain name and the second with just
If the command
hostname --fqdn returns
Unknown host do the following:
- Select
- Click on
Click to make changes
- Enter
<wwadmin password>and click
- Click on
- Select the entry with your server's IP address and click
- Under Aliases you should see your server's fully qualified domain name, something like
- Select the entry
127.0.0.1and click
- Under Aliases make sure you have the following entries in order
- first your server's fully qualified domain name, something like
- second your server's name, something like
- third
- first your server's fully qualified domain name, something like
- Click
Addand add an entry with
IP address
127.0.1.1and under
Aliasesput your server's fully qualified domain name, something like
- Then click
- And click
Closeto close
Network settings
Then check again by running the commands
$ hostname --fqdn
$ hostname
Note that if your server can not find its fully qualified domain name, certain tools (such as the Synaptic Package Manager) will not start.
Now restart Apache
$su <root password> # apache2ctl graceful # exit $
and test your server by connecting to "http://localhost/" and/or connecting to your server from a browser on a remote machine. You should see the page It works! indicating that Apache is running.
You can check Apache's status by connecting to "http://localhost/server-status" using a browser on your machine or from a browser on a remote machine in the math.yourschool.edu domain.
Further test Apache by connecting to
"http://localhost/server-info" using a browser on your machine (or or from a browser on a remote machine in the math.yourschool.edu domain) and you will see a page listing various
information about Apache. In particular under
Server Settings you should see
Server Version: Apache/2.2.14 (Ubuntu) mod_apreq2-20051231/2.6.0 mod_perl/2.0.4 Perl/v5.10.1
indicating that both
mod_apreq2 and
mod_perl are installed.
If you have problems now or in the future, a good first thing to do is to look at the Apache error log which is located at
/var/log/apache2/error.log. In the directory
/var/log/apache2/ you can "less" through the error log (
less error.log), look at the last few entires (
tail error.log) or run the command
tail -f error.log which will display new error messages as they are appended to the file. Use
^C to break out of
tail -f .
Checking MySQL
First check that MySQL is running by
$ mysql -u root -p Enter Password: <mysql root password>
You should see something very similar to
Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 33 Server version: 5.1.41-3ubuntu12.10 (Ubuntu) Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
exit to exit
mysql> exit Bye $
Reboot and Test
Now reboot the system (click on the start/stop button icon in the upper right hand corner, then select
Now connect to "http://localhost/" using a browser on your machine and/or to your server from a browser on a remote machine. You should see the page It Works indicating that Apache is running.
This is also a good time to check that you can login your server from a remote location using SSH (non secure telnet and FTP are not allowed but secure SSH and SFTP are). If you are using "SSH Secure Shell" (now called "SSH Tectia"), a popular SSH client for PC's, you will have to add
Keyboard Interactive to the list of "Authentication methods" under "Authentication" if it's not already there.
Finally test that MySQL is running.
$ mysql -u root -p Enter Password: <mysql root password> ... mysql>
Now lets check the MySQL users.
There are three root accounts, one is
root@localhost, one is
firstname.lastname@example.com and the third is
root@host_name where
host_name is the name of your server. To find see name, do the following
mysql> SELECT Host, User, Password FROM mysql.user;
You will see a table with four users (three
root and one
You should see that all four users have passwords (which will be displayed in encrypted form).
Now exit MySQL
mysql> exit Bye $
Congratulate yourself. You are now ready for the next and hopefully easy part, installing WeBWorK.
Downloading the WeBWorK System Software and Problem Libraries
We are finally at the point where we can start downloading and installing WeBWorK. We will use Subversion to download WeBWorK. This is easy and it will also make it easy to update the system in the future. Note that the following are rather long commands; it is much easier to copy (
^C) them from this document and paste (
<Shift> <Ctrl> <V>) them in a terminal window
$ cd $ cd downloads $ svn co http://svn.webwork.maa.org/system/trunk/webwork2 $ svn co http://svn.webwork.maa.org/system/trunk/pg $ svn co http://svn.webwork.maa.org/npl/trunk/NationalProblemLibrary
The first and second download gives you the latest released version with patches. The third download contains the WeBWorK National Problem Library. This now includes the Rochester and Union Libraries along with others as sub libraries. Your system will be loaded with many thousands of WeBWorK problems (over 22,000 currently).
The main information page about WebWork downloads is available at http://webwork.maa.org/wiki/Download
The main information page about the NPL is available at http://webwork.maa.org/wiki/National_Problem_Library
Installing WeBWorK
Note the the instructions below assume you are installing WeBWorK from scratch. If you are just upgrading WeBWorK, especially if you already have existing WeBWorK courses, see Upgrading WeBWorK.
Move the System into the Required Directories
root create a
webwork directory under
/opt, change the ownership of the
webwork directory to
wwwadmin and move directories there.
$ sudo mkdir /opt/webwork <wwadmin password> $ sudo chown wwadmin:wwadmin /opt/webwork $ mv webwork2 /opt/webwork/ $ mv pg /opt/webwork/
Now create the
courses and
libraries directories under
webwork and copy and move content there being careful not to copy the .svn directories
$ mkdir /opt/webwork/courses $ mkdir /opt/webwork/libraries $ mv NationalProblemLibrary /opt/webwork/libraries/ $ cd /opt/webwork/webwork2/courses.dist $ cp *.lst /opt/webwork/courses/ $ rsync -a --exclude '.svn' modelCourse /opt/webwork/courses/
Setting Permissions
The PG installation directory and files should be owned by
wwadmin and not writable by other users:
$ cd /opt/webwork/pg $ chmod -R u+rwX,go+rX .
Most WeBWorK directories and files should also be owned by
wwadmin and not writable by other users:
$ cd /opt/webwork/webwork2 $ chmod -R u+rwX,go+rX .
Certain data directories need to be writable by the web server. These are
logs, and
tmp. It is convenient to give WeBWorK administrators access to these directories as well, so they can perform administrative tasks such as removing temporary files, creating and editing courses from the command line, managing logs, and so on. We will create a new group called
wwdata, containing both the WeBWorK administrators and the web server.
- Select
Administrationand then
Users and Groups
- Click on
Manage Groups
- Click
- Enter
<wwadmin password>and click
- For
Group nameenter
- For
Group IDaccept the default which is probably 1001
- Under
Group Memberscheck wwadmin and click
- Click
If there are other users who will also be administering WeBWorK files,
now is a good time to add them. And remember to add them to the
wwdata group as above. When finished
- Click
Because system users are not shown by default, we can not simply use the
Group Manager to add the Apache2 webserver (which runs as
www-data) to the
group so we will do this by hand as root.
$ su Password: <root password> # cd /etc # cp group group.bak1 # gedit group
- In the gedit window scroll to the last line.
- It should look like
wwdata:x:1001:<wwadmin userid>
- Append to this line
- Then Save and Quit
You can check that this succeeded in a terminal window by entering
# exit $ id wwadmin
and then you should see
wwdata listed under groups. Also
$ id www-data
should show wwdata listed under groups. Now we make the WeBWorK directories that need to be writable by the web server have
wwdata as their group. The following are rather long commands; you might want to copy them and paste them into your terminal window rather than typing them.
$ su Password: <root password> # cd /opt/webwork/webwork2/ # chgrp -R wwdata DATA ../courses htdocs/tmp logs tmp # chmod -R g+w DATA ../courses htdocs/tmp logs tmp # find DATA/ ../courses/ htdocs/tmp logs/ tmp/ -type d -a ! \( -name .svn -prune \) -exec chmod g+s {} \; # exit $
Configuring the Shell
To make working with WeBWorK easier, there are a couple of changes you can make to your shell environment.
Add the WeBWorK
bin directory to your path. This will allow you to run WeBWorK command-line utilities without typing the full path to the utility. Goto your home directory and backup your
.bashrc file
$ cd $ cp .bashrc .bashrc.bak1
Now edit
$ gedit .bashrc
After the last line add the three lines:
export PATH=$PATH:/opt/webwork/webwork2/bin export WEBWORK_ROOT=/opt/webwork/webwork2 export PG_ROOT=/opt/webwork/pg
Then save the file and Quit.
Close your Terminal Window and open a new one so the above changes take effect. You can check that they have by
$ echo $PATH $ echo $WEBWORK_ROOT $ echo $PG_ROOT
Checking Module Dependancies
WeBWorK includes a script called
check_modules.pl that verifies that the needed programs and Perl modules are installed on your system. Run this script to make sure you have installed the required programs and Perl modules.
$ check_modules.pl apache2
Scroll up and look through the listing. It should find everything except
tth which is a deprecated display mode. If something is missing (flagged by
**), look back through these instructions and/or look at Installation Manual for 2.4 to find where it should have been installed and install it. Note you may have to search in Installation Manual for 2.4 to find out what package it is contained in.
Configuring WeBWorK
Making Copies of the Distribution Configuration Files
Before configuring the system, you must make local copies of the
global.conf and
database.conf configuration files, located in
/opt/webwork/webwork2/conf/ .
$ cd /opt/webwork/webwork2/conf $ cp global.conf.dist global.conf $ cp database.conf.dist database.conf
Global Configuration
Most WeBWorK configuration is done in the file
/opt/webwork/webwork2/conf/global.conf. This file provides system-wide configuration settings, and defaults for course settings. Any setting in this file can be overridden in the
course.conf file for a particular course. To override a setting for a course, just put the new setting (using the same syntax as is in
global.conf) in the
course.conf file.
There are several options that must be set for WeBWorK to work with your system. The rest of the file consists of customization options. Now edit
$ cd /opt/webwork/webwork2/conf $ gedit global.conf
WeBWorK uses the DateTime module. DateTime is supposed to be able to determine the local timezone itself without you having to enter it but this often fails so it is best to just set it here. For is a list of timezones recognized by DateTime go to
http://search.cpan.org/dist/DateTime-TimeZone/ . These timezones are more refined than standard timezone usage in that they include switches to daylight savings time (e.g. some parts of a time zone may make the switch and others may not). For example if your server is in the eastern US, on the list you will see
DateTime::TimeZone::America::New_York and you should enter
$siteDefaults{timezone} = "America/New_York"; which is the default.
- Search for
$siteDefaults{timezone}and enter your local timezone if it is not correct.
Since we have installed
MathJax we need to add it as a possible display mode.
- Search for
render TeX math expressions on the client side using MathJaxand uncomment whole line
so it becomes
"MathJax", # render TeX math expressions on the client side using MathJax --- we strongly recommend people install and use MathJax
We need to set a password that WeBWorK uses when it communicates with the MySQL database. Note that this is not the same as the
<mysql root password> which is the password the MySQL root user uses.
- Search for
$database_password = "";and replace this by
$database_password = "database_password";
where of course you should replace 'database_password' with your own password. Remember this password as we will need it below.
WeBWorK sends mail in three instances. The PG system sends mail to report answers to questionnaires and free-response problems. The mail merge module is used to send mail to course participants, i.e. to report scores. The feedback module allows participants to send mail to course instructors.
To send mail, WeBWorK needs the address of an SMTP server. Normally you will use the address of your school's SMTP server. If the local machine is running an SMTP server, use
localhost. IMPORTANT: Our instructions above did not install an SMTP server so you will have to install and configue one if you do not use your school's SMTP server. When connecting to the SMTP server, WeBWorK must also send an email address representing the sender of the email (this has nothing to do with the
From address on the mail message). Edit the lines
$mail{smtpServer} = 'mail.yourschool.edu'; $mail{smtpSender} = 'firstname.lastname@example.com';
entering the appropriate information.
If you want WeBWorK questionnaires or similar things from different courses to be mailed to a central person or persons (e.g. the WeBWorK administrator), edit the lines
$mail{allowedRecipients} = [ #'email@example.com', #'email@example.com', ];
appropriately removing the
# and using the professor(s) actual email address(es). In order to have professors from individual courses receive such email, this
should be set in course.conf (which you find in the course directory) to the addresses of professors of each course. Note that the settings in course.conf override the settings in global.conf, so if in addition you want e.g. the WeBWorK administrators to receive copies, you have to add them as well.
Finally we have to add information about the Apache2 server setup.
- Search for
$server_root_urland edit the three lines so that they read:
$server_root_url = "http://yourserver.yourschool.edu"; $server_userID = "www-data"; $server_groupID = "wwdata";
where of course you should edit
yourserver.yourschool.edu appropriately.
Then save the file and Quit.
WeBWorK uses a single database, called
webwork, for all courses. We will create the
webwork database now.
To do this do the following (before you just copy, paste and hit
<Enter> notice that you have to replace
database_password with the password you set when editing
global.conf above):
$ mysql -u root -p mysql Enter password: <mysql root password> mysql> CREATE DATABASE webwork; mysql> GRANT SELECT, INSERT, UPDATE, DELETE, CREATE, ALTER, DROP, LOCK TABLES ON webwork.* TO webworkWrite@localhost IDENTIFIED BY 'database_password'; mysql> exit Bye $
where as we said replace
database_password with the password you set when editing
global.conf above.
jsMath Settings
Version 2.0 of jsMath introduced a new fallback method for when the TeX fonts are not available on the student's computer. This uses images of the individual TeX characters in place of the TeX fonts. These are distributed in
webwork2/htdocs/jsMath/jsMath-fonts.tar.gz, and you need to unpack this tarball before jsMath will work properly. Use the command
$ cd /opt/webwork/webwork2/htdocs/jsMath $ tar vfxz jsMath-fonts.tar.gz
This will unpack the archive. Since there are 20,000 tiny files, it can take a little while, so the
v option is used to show you the names as they are unpacked so that you know the command is actually doing something. Once the images are unpacked, jsMath's image mode fallback (the default fallback method) will work properly.
General information on MathJax can be found at http://www.mathjax.org/ and general installation instructions are at http://www.mathjax.org/resources/docs/?installation.html . MathJax is already installed in the location
Configuring Apache
WeBWorK ships with an Apache config file that needs to linked into your Apache configuration process. The file is named
webwork.apache2-config.dist and located in the
conf directory. First, copy the file to
$ cd /opt/webwork/webwork2/conf $ cp webwork.apache2-config.dist webwork.apache2-config
and now link it into your Apache configuration process
$ su <root password> # cd /etc/apache2/conf.d # ln -s /opt/webwork/webwork2/conf/webwork.apache2-config webwork.conf
Next we will make a few changes to Apache's default configuration. First we backup the configuration file
# cd /etc/apache2/ # cp apache2.conf apache2.conf.bak1 # gedit apache2.conf
Search for the line
Timeout 300
and replace it by
Timeout 1200
Next seach for the lines
MaxClients 150 MaxRequestsPerChild 0
Which occur under
<IfModule mpm_prefork_module> and replace them by
# For WeBWorK a rough rule of thumb is 20 MaxClients per 1 GB of memory MaxClients 20 MaxRequestsPerChild 100
where you should set
MaxClients depending on the amount of memory your server has using the above rule of thumb.
Then save the file and quit.
Finally we copy WeBWorK's icon file
favicon.ico to Apache's
www directory.
# cp /opt/webwork/webwork2/htdocs/favicon.ico /var/www
Now restart Apache
# apache2ctl graceful # exit $
Test your configuration
- Test the
/webwork2location by visiting
http://yourserver.yourschool.edu/webwork2. You should see the WeBWorK home page with no courses listed. Actually the directory
/opt/webwork/courses/does contain the
modelCoursebut the
modelCourseis not a real course so you will get an error message if you try to log into it. It will be used a as model for setting up other courses. For this reason
/opt/webwork/courses/modelCourse/contains a file named
hide_directoryand so the
modelCourseis not visible.
- Test the
/webwork2_fileslocation by visiting
http://yourserver.yourschool.edu/webwork2_files. You should see the "WeBWorK Placeholder Page".
- You cannot test the
/webwork2_course_fileslocation until you have created a course.
If Something is Wrong
If something is wrong one of the first things to check is that the config files have been edited correctly (e.g. one time a wrapped line in
global.conf caused me problems, another time it was a missing single quote). A quick way to check this is to do a
diff between the edited and distributed versions and check that
diff reports the changes you made and only those.
# exit $ $ cd /etc/apache2/ $ diff apache2.conf apache2.conf.bak1 $ cd /opt/webwork/webwork2/conf/ $ diff global.conf global.conf.dist $ diff database.conf database.conf.dist $ diff webwork.apache2-config webwork.apache2-config.dist
If something is wrong and you fix it, you will have to restart Apache for the changes to take effect
$ su <root password> # apache2ctl graceful # exit $
Create the admin Course
Course Administration gives information about creating courses. Here we will give explicit instructions for doing this.
$ newgrp wwdata $ umask 2 $ cd /opt/webwork/courses $ /opt/webwork/webwork2/bin/addcourse admin --db-layout=sql_single --users=adminClasslist.lst --professors=admin $ exit
Now goto
http://yourserver.yourschool.edu/webwork2 and should see the WeBWorK home page with
Course Adninistration listed at the top. Click on it and login with Username
admin and Password
admin . This first thing you should do is register your new WeBWorK installation. It's quick and easy, just click on
Register. The next thing you should do is click on
Password/Email and change
admin 's password to something more secure than
admin .
Unless you choose oherwise, users with
professor privilges in the
admin course (i.e. WeBWorK administrators) will automatically be added to new courses with
professor privilges and the same password as in the
admin course. Initially the only such user is
admin (hopefully you are not confused by the fact that the course
admin has a user named
admin). It's usually convenient make yourself a WeBWorK administrator. To do this (assuming you are logged in as
admin to the
admin course at
http://yourserver.yourschool.edu/webwork2/admin )
- Click on
Classlist Editorin the left panel
- Check
Add 1 student(s)and click
Take Action!
- Enter the appropiate information (you can leave the last three items blank) and click
Add Students
- Click on
Classlist Editorin the left panel again
- When you enter a new student, by default their
Student IDis used as their password. We'll change this now.
- Select yourself with a check mark and then check
Give new password to Selected usersor just check
Give new password to All users(as a safely mechanism you can not change the password for the user you are logged in as, currently
admin, this way) and then click
Take Action!
- Enter the password, check
Save changesand then click
Take Action!
- Finally give yourself
professorprivilges by selecting yourself with a check mark, checking
Edit Selected usersand then clicking
Take Action!(or by just clicking on the "pencil" next to your login name which is a much faster way to edit classlist data for a single user)
- Now at the far right change
Permission Levelfrom
- Check
Save changesand then click
Take Action!
At some point you will probably want to hide the
admin course so that it is not listed on the WeBWorK home page. As we noted above the
modelCourse, which is already hidden, is not a real course so you will get an error message if you try to log into it. This is a good reason to hide it. The
modelCourse is very useful as a model (hence its name) for setting up other courses. The
admin course is used for administering WeBWorK and even though regular users can not log into it (you did change the
admin password, didn't you!!), it a little bit cleaner and safer to hide it from prying eyes.
To hide a course place a file named
hide_directory in the course directory and it will not show up in the courses list on the WeBWorK home page. It will still appear in the Course Administration listing. If you do this you will still be able to access the
admin course using the URL
http://yourserver.yourschool.edu/webwork2/admin but you will not see a link for it on the WeBWorK home page
http://yourserver.yourschool.edu/webwork2 . Let's hide the
admin course.
$ cp /opt/webwork/courses/modelCourse/hide_directory /opt/webwork/courses/admin
Now goto
http://yourserver.yourschool.edu/webwork2 and no course will be listed.
Starting and Stopping Apache, MySQL and the GNOME desktop GUI
If you make changes to the system, you will have to restart
apache2 before the changes take effect. On rare occasions you may need to restart
Starting and Stopping Apache
You have to run these commands as
To start or restart (i.e. stop and then start) the
apache2 webserver run the command
$ sudo apache2ctl graceful password:<wwadmin password>
You can also start
apache2 by
$ sudo apache2ctl start password:<wwadmin password>
and restart it with
$ sudo apache2ctl restart password:<wwadmin password>
restart is less graceful but more powerful than
graceful. Sometimes
graceful fails to kill all
apache2 child processes.
To stop the Apache webserver run the command
$ sudo apache2ctl stop password:<wwadmin password>
You can also start or stop apache2 by using the
init.d script
apache2. Run
$ sudo /etc/init.d/apache2 password:<wwadmin password>
and you will get a list of allowed commands (
restart, etc).
Starting and Stopping MySQL
You have to run these commands as
To start the
MySQL server run the command
$ sudo /etc/init.d/mysql start password:<wwadmin password>
To stop the
MySQL server run the command
$ sudo /etc/init.d/mysql stop password: <wwadmin password>
To restart the
MySQL server run the command
$ sudo /etc/init.d/mysql restart password: <wwadmin password>
Starting and stopping the GNOME desktop GUI
The GNOME desktop is automatically started when the system boots.
To stop
GNOME so that you only have a standard terminal window run the following in a standard terminal window
$ sudo /etc/init.d/gdm stop password: <wwadmin password>
If you stopped
GNOME and want to restart it run the following in a standard terminal window
$ sudo /etc/init.d/gdm start password: <wwadmin password>
Install the WeBWorK Problem Libraries
Before we create a real course we will install the WeBWorK Problem Libraries.
Install the National Problem Library
National Problem Library consists of both WeBWorK problems and methods for searching and selecting problems. Also it contains as sub libraries many of the other standard libraries. We have to tell WeBWork where to find it.
$ cd /opt/webwork/webwork2/conf $ gedit global.conf
Search for
problemLibrary and replace
$problemLibrary{root} = ""; by
$problemLibrary{root} = "/opt/webwork/libraries/NationalProblemLibrary";
Then save the file and quit.
Run the
NPL-update script making sure you are in the
/opt/webwork/libraries/NationalProblemLibrary directory. This directory contains the files
loadDB2 and
$ cd /opt/webwork/libraries/NationalProblemLibrary $ NPL-update
This has to convert a lot of data for over 20,000 problems so please be patient; it can take a long time.
If at some time in the future you want to upgrade the Problem Library, the process is simpler. Optionally remove the previous copy of the library, unpack the new copy in the same place, and run NPL-update.
Finally we put a link to the National Problem Library in the modelCourse so that when we create courses copying templates from the modelCourse, the NPL will be available.
$ cd /opt/webwork/courses/modelCourse/templates/ $ ln -s /opt/webwork/libraries/NationalProblemLibrary Library
Set up the Rochester and Union Libraries
This step is optional. It creates buttons in the Library Browser which give direct links to the Rochester and Union libraries. If you don't do this, you can find these libraries and others under the
NPL Directory button.
First we need to edit
global.conf one last time
$ cd /opt/webwork/webwork2/conf $ gedit global.conf
Search for
courseFiles{problibs} and scroll down several lines to the lines
# rochesterLibrary => "Rochester", # unionLibrary => "Union",
Uncomment these lines (i.e. remove the
#) so they become
rochesterLibrary => "Rochester", unionLibrary => "Union",
Then save the file and quit.
We next put links to the Rochester and Union Libraries in the
modelCourse so that when we create courses copying templates from the
modelCourse, these libraries will be available. Skip this step if you usually only want to use National Problem Library. Note that the Rochester, Union and other libraries are contained in the National Problem Library and are accessible from there under the
NPL Directory button in the Library Browser. This step simply creates buttons in the Library Browser so that you can access the Rochester and Union libraries directly.
$ cd /opt/webwork/courses/modelCourse/templates/ $ ln -s /opt/webwork/libraries/NationalProblemLibrary/Union unionLibrary $ ln -s /opt/webwork/libraries/NationalProblemLibrary/Rochester rochesterLibrary
If you want to put another library into the
modelCourse, just do the analogous thing. If you just want the additional library in a particular course, add the link in the
templates directory of that course. If you look in the directory
/opt/webwork/libraries/NationalProblemLibrary/ you might find other libraries that are not yet listed in
global.conf and these can be added in the same way as the
Rochester and
Union libraries. Finally if you add a library with non standard symbols in the name (e.g.
uva-statLibrary) you have to use single quotes when adding it to
global.conf, e.g.
'uva-statLibrary' => "UVA-Stat",
It's easier to just avoid such names.
Install and Set Up the CAPA Library
This step is optional. It installs and sets up the CAPA Library, which is a library of physics problems.
First we download the CAPA Library including required macros.
$ cd $ cd downloads $ svn co http://svn.webwork.maa.org/rochester/trunk/rochester_physics_problib
Create a
CAPA directory under
/opt/webwork and move the CAPA macros there. Then move the CAPA graphics and library files to the required locations and set the group.
$ mkdir /opt/webwork/libraries/CAPA $ cd rochester_physics_problib/macros/ $ mv CAPA_Tools /opt/webwork/libraries/CAPA/ $ mv CAPA_MCTools /opt/webwork/libraries/CAPA/ $ cd .. $ mv CAPA_Graphics /opt/webwork/webwork2/htdocs/ $ sudo chgrp -R wwdata /opt/webwork/webwork2/htdocs/CAPA_Graphics password: <wwadmin password> $ sudo chmod -R g+w /opt/webwork/webwork2/htdocs/CAPA_Graphics $ cd .. $ mv rochester_physics_problib /opt/webwork/libraries/
We need to edit
global.conf again
$ cd /opt/webwork/webwork2/conf $ gedit global.conf
Search for
courseFiles{problibs} and scroll down several lines to the line
# capaLibrary => "CAPA",
Uncomment this line (i.e. remove the
#) so it becomes
capaLibrary => "CAPA",
Next search for
Locations of CAPA resources and, if necessary, edit the four following lines
so that they read as follows (cut and paste is the best way to do this)
$pg{specialPGEnvironmentVars}{CAPA_Tools} = "/opt/webwork/libraries/CAPA/CAPA_Tools/", $pg{specialPGEnvironmentVars}{CAPA_MCTools} = "/opt/webwork/libraries/CAPA/CAPA_MCTools/", $pg{specialPGEnvironmentVars}{CAPA_GraphicsDirectory} = "$webworkDirs{htdocs}/CAPA_Graphics/", $pg{specialPGEnvironmentVars}{CAPA_Graphics_URL} = "$webworkURLs{htdocs}/CAPA_Graphics/",
Then save the file and quit. Note that we are setting up the CAPA macros and graphics so that they can be used by any WeBWorK course on the server.
There is one final step that is needed. We have to put a link in the templates directory of every course that needs access to the CAPA Library. If you want to have every course you create have access to the CAPA Library (unlikely unless you are in a physics department) put the link in the
$ cd /opt/webwork/courses/modelCourse/templates/ $ ln -s /opt/webwork/libraries/rochester_physics_problib/ capaLibrary
More likely you just want to do this for individual courses. We don't have any yet. But for example after creating
myTestCourse below, to set up access to the CAPA Library from
myTestCourse, do the following
$ cd /opt/webwork/courses/myTestCourse/templates/ $ sudo ln -s /opt/webwork/libraries/rochester_physics_problib/ capaLibrary password: <wwadmin password>
and do the analogous thing for every course that needs access to the CAPA Library. Then to gain access to the CAPA Library from the course, simply go to the
Library Browser and click on the
CAPA button.
Create Your First Actual Course
Since we have edited
global.conf a lot and this is a very critical file, it would be a good idea to run
$ cd /opt/webwork/webwork2/conf $ diff global.conf global.conf.dist
and check that you haven't made any mistakes (e.g. by introducing an inadvertent line break, etc). If there are any mistakes, correct them. Remember that any time you change
global.conf, you must restart the Apache webserver in order for these changes to take effect.
Since we have edited
global.conf extensively and haven't restartes Apache we do so now.
$ sudo apache2ctl graceful password:<wwadmin password>
Now log into the
admin course (
http://yourserver.yourschool.edu/webwork2/admin ) as yourself or
admin and
- click on
Add Course
- For
Course IDenter
- For
Course Titleenter
My Test Course
- Enter your institution
- Leave
Add WeBWorK administrators to new coursechecked
- Add an additional instructor if you wish
- Copy templates from:
modelCourse(the default action)
- Select sql_single for the database layout (the default action)
- Click on
Add Course
- Click
Log into myTestCourse
and log in either as
admin or yourself.
At some point you will probably want to "hide"
myTestCourse from general view but you already know how to do that.
Test that Things are Working Properly
We will test out a few important parts of WeBWorK. If you run into problems, you should look at the Apache error log which is located at
Click on
Hmwk Sets Editor on the
Main Menu. Then select (by clicking the circle button)
Import, select
setDemo.def from the
from drop down list and select
all current users from the
assigning this set to drop down list. Then hit
Take Action!
Now click on
Homework Sets on the
Main Menu and click on
Demo. Then look at the problems. Mathematical equations should be typeset. If not, edit the file
Constants.pm in the directory
/opt/webwork/webwork2/lib/WeBWorK. Change the line
$WeBWorK::PG::ImageGenerator::PreserveTempFiles = 0; to
...::PreserveTempFiles = 1;. Then restart Apache and view the first couple problems or some new ones. Then look in the directory
cd to one of the
ImageGenerator.../tmp/ directories and look at the error and log files there. When you fix the problem remember to edit
...::PreserveTempFiles = 1; back to 0 and restart Apache or you will be saving a lot of unnecessary files. Another useful trick is to try downloading a hard copy of an assignment and then (assuming there are errors) looking at the various log files that are linked to on the output page.
When you continue looking at problems you will probably get an error when you try to look at Problem 6 because you may not have configured the CAPA macros which are required to display CAPA problems. Unless you are teaching physics you probably don't need them. Also in Problem 9 the Java applet will not load. Problem 9 was written in the 90's and used an applet on a server at The Johns Hopkins University. The server went away a long time ago but we have retained this problem for historical reasons and also because it is a example of several things (e.g. WeBWorK problems can include applets running on remote servers but this can lead to other problems).
Next click on
Prob. List to bring back the Problem List Page and click on
Download a hardcopy of this homework set. The page is a little complicated because you are a professor (students see a very simple page) but you can just scroll to the bottom and click on
Generate hardcopy for selected users and selected sets. You will get an error (because of the bad Problem 6) but just click
Download Hardcopy to get what was generated. Also you can see links to various
informational files that are available if you run into problems (normally these files are removed if there are no errors).
Another thing to do is to use
Main Menu. Again this page is a little complicated because you can do a lot of things with it (including mail merge) but at this point just select yourself in the list to the right and hit
Send Email at the bottom. You should receive two emails. One is the message you just sent and the other is an email with subject "WeBWorK email sent" giving information on your mailing.
As a final test click on
Library Browser on the
Main Menu. Click
Problem Library
and select a
Chapter and
Section and then hit
View Problems. The first 20 of your selected problems will be displayed. You can also test that you can access any additional Problem Libraries that you installed.
If all the above tests work, you can be pretty confident that WeBWorK is working properly.
Go back to
Hmwk Sets Editor on the
Main Menu. Then select (by clicking the circle button)
Import, select
setOrientation.def from the
from drop down list and select
all current users from the
assigning this set to drop down list. Then hit
Take Action!. Then go through the Orientation problems. This is a good first set to use for introducing students to WeBWorK.
If you are new to WeBWorK, you should probably add a regular student to myTestCourse and log in as that student to see what the student interface looks like. It's much simpler than the professor interface.
Click on
Classlist Editor on the
Main Menu.
Then select (by clicking the circle button)
Add 1 student(s)and hit
Take Action!. Add one student, say Jane Smith, with
Student ID
1234 and
Login Name
Jane Smith's initial password will be her
Student ID
1234. Now login as Jane Smith and play around a little.
Optional Configurations
Optional A stores WeBWorK's "temporary" files in a separate partition. Optional B installs and configures a lightweight webserver to serve static files. Optional C configures Apache so that access to WeBWorK will be through SSL.
Implement Optional A (wwtmp)
Now is the time to implement Optional A if you choose to do so. Actually you can do this at any time and your active courses will continue to function seemingly without change. The only change behind the scenes will be that temporary files will be stored in a different location. Note that if you want to use this option but did not create
wwtmp. as a separate partition, you first have to create the directory
First we set the group and permissions for the
wwtmp directory
$ su <root password> # cd /var/www # chgrp wwdata wwtmp # chmod ug+w wwtmp # chmod g+s wwtmp # exit $
Next we have to edit
global.conf so that WeBWorK uses the new
wwtmp directory. Since we have a working WeBWorK system, first we make a backup copy of
$ cd /opt/webwork/webwork2/conf $ cp global.conf global.conf.bak1 $ gedit global.conf
Now edit
global.conf. Find the lines
$webworkDirs{htdocs_temp} = "$webworkDirs{htdocs}/tmp"; $webworkURLs{htdocs_temp} = "$webworkURLs{htdocs}/tmp";
and replace them by
#$webworkDirs{htdocs_temp} = "$webworkDirs{htdocs}/tmp"; #$webworkURLs{htdocs_temp} = "$webworkURLs{htdocs}/tmp"; $webworkDirs{htdocs_temp} = '/var/www/wwtmp'; $webworkURLs{htdocs_temp} = '/wwtmp';
Next find the lines
$courseDirs{html_temp} = "$courseDirs{html}/tmp"; $courseURLs{html_temp} = "$courseURLs{html}/tmp";
and replace them by
#$courseDirs{html_temp} = "$courseDirs{html}/tmp"; #$courseURLs{html_temp} = "$courseURLs{html}/tmp"; $courseDirs{html_temp} = "/var/www/wwtmp/$courseName"; $courseURLs{html_temp} = "/wwtmp/$courseName";
Then save the file and quit. If you look at the
wwtmp directory you will find it empty but after you restart apache and then access some WeBWorK problems, you will find temporary directories and files in
wwtmp. Remember your have to restart apache for these changes to take effect.
Implement Optional B (lighttpd)
As is the case for Optional A you can implement Optional B at any time and your active courses will continue to function seemingly without change. The only change behind the scenes will be that static images and pages will be served by a light weight web server.
First we install the light weight webserver
- Open the
Synaptic Package Manager(select
Synaptic Package Manager).
- Select
- Search for
lighttpdand select it
- In the pop up window
Mark additional required changes?click
Markto accept the requirements.
- Now click
Applyagain to confirm the changes.
You can now quit the
Synaptic Package Manager.
Now we configure
lighttpd. First let's make a backup of the configuration file.
$ su <root password> # cd /etc/lighttpd # cp lighttpd.conf lighttpd.conf.bak1
Now edit
# gedit lighttpd.conf
Uncomment the line
# "mod_status",
so it becomes
Apache2 is listening on port 80 so we need an alternate port for lighttp to listen to. Standard alternate ports for this are usually 81, 8000, or 8080. 8080 is the only port that is listed as an official alternate at http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers . Note that in rare cases an installation may block httpd requests to port 8080. If any of your students report that they can not see graphics, they will have to request that access to requests to port 8080 be allowed.
Find the line
# server.port = 81
uncomment it and change 81 to 8080 so that it reads
server.port = 8080
Finally uncomment the line
# status.status-url = "/server-status"
so it becomes
status.status-url = "/server-status"
Then save the file and quit.
Now restart lighttp
$su <root password> # /etc/init.d/lighttpd restart # exit $
Note that you can just run
/etc/init.d/lighttpd to get a list of all options.
Now test your server by connecting to "http://localhost:8080/" and/or connecting to your server from a browser on a remote machine. You should see the page It works! indicating that lighttp is running.
You can check lighttp's status by connecting to "http://localhost:8080/server-status" using a browser on your machine or from to "http://yourserver.yourschool.edu:8080/server-status" from a browser on a remote machine.
The Server-Status page doesn't indicate that lighttp is the web server, but it's certainly different than apache's Server-Status page "http://localhost/server-status".
Next we configure WeBWorK to take advantage of lighttp.
First let's make a backup copy of
global.conf so that we can easily back out of these changes if necessary.
# cd /opt/webwork/webwork2/conf # cp global.conf global.conf.bak2
Now edit
global.conf. Note that while Optional B is independent of Optional A, we assume most people implementing Optional B will have already implemented Optional A. Therefore we give instructions for editing
global.conf assuming that Optional A has been implemented. If this is not the case, modify the instructions below accordingly. Also replace
yourserver.yourschool.edu with the correct address.
# gedit global.conf
Find the line
$webworkURLs{htdocs_temp} = '/wwtmp'
and replace it by
#$webworkURLs{htdocs_temp} = '/wwtmp'; $webworkURLs{htdocs_temp} = 'http://yourserver.yourschool.edu:8080/wwtmp';
Find the line
$courseURLs{html_temp} = "/wwtmp/$courseName";
and replace it by
#$courseURLs{html_temp} = "/wwtmp/$courseName"; $courseURLs{html_temp} = "http://yourserver.yourschool.edu:8080/wwtmp/$courseName";
Then save the file and quit.
Now restart apache and lighttp.
$ sudo apache2ctl graceful password:<wwadmin password> $ sudo /etc/init.d/lighttpd restart
To test things go to your test course
http://yourserver.yourschool.edu/webwork2/myTestCourse/. Before you login right click on the WeBWorK icon in the upper left hand corner of the login page. The click on Properties (or whatever is appropriate on your browser) and check that the image is being served from port 8080 (something like
http://yourserver.yourschool.edu:8080/webwork2_files/images/webwork_rectangle.png. Then log into your course and view a problem with typeset equations (e.g. Problem 1 of the Demo set). Again right click on the typeset equation and check that the image is being served from port 8080.
Implement Optional C (SSL)
Optional C configures apache so that access to WeBWorK will be through an encrypted Secure Sockets Layer (SSL) with an https: URL. Note that if you implemented Optional B, the non encrypted lighttp server will be used for images, etc but there is no harm in that.
I cribbed these directions from several sources, the main one being http://www.akadia.com/services/ssh_test_certificate.html.
We will create and work in a
tmp directory.
$ cd $ mkdir tmp $ cd tmp
First we create an RSA Private Key.
$ openssl genrsa -des3 -out server.key 1024
When you are asked for a
pass phrase, enter a phrase which we refer to as
<my pass phrase> and then confirm it. Next generate a Certificate Signing Request
$ openssl req -new -key server.key -out server.csr
Enter the requested information. Important: when you are prompted for the
Common Name enter your server's fully qualified domain name, something like
yourserver.yourschool.edu. You can leave the last two items
A challenge password []: An optional company name []:
One unfortunate side-effect of the pass-phrased private key is that Apache will ask for the pass-phrase each time the web server is started. Obviously this is not necessarily convenient as someone will not always be around to type in the pass-phrase, such as after a reboot or crash. We will remove this but you must keep this file secure.
$ cp server.key server.key.bak1 $ openssl rsa -in server.key.bak1 -out server.key
Next we generate a self-signed certificate which is good for 365 days
$ openssl x509 -req -days 365 -in server.csr -signkey server.key -out server.crt
Now we become root, move these files, and set their group and permission.
$ su <root password> # mv server.crt /etc/ssl/private # mv server.key /etc/ssl/private # cd /etc/ssl/private # chgrp ssl-cert server.* # chmod 640 server.*
Next we enable the
mod_ssl module
# a2enmod ssl
Now we have to configure Apache to use SSL.
# cd /etc/apache2/sites-available/ # cp default default.bak1 # gedit default
Replace the first line
NameVirtualHost *
by the two lines
NameVirtualHost *:80 NameVirtualHost *:443
Now edit the next non blank line
<VirtualHost *>
changing it to
<VirtualHost *:80>
Next copy the entire section
<VirtualHost *:80> ... </VirtualHost>
(that is the whole VirtualHost section to the end of the file) and paste it into the file at the end of the file. Now we edit this new pasted section. Edit the new second
<VirtualHost *:80>
changing it to
<VirtualHost *:443>
Now at the end of the file just above the line
add the three lines
SSLEngine on SSLCertificateFile /etc/ssl/private/server.crt SSLCertificateKeyFile /etc/ssl/private/server.key
Then save the file and quit. Finally we restart Apache
# apache2ctl graceful
and test things. Connect to https://yourserver.yourschool.edu/webwork2/myTestCourse You will be asked to accept the certificate. After you do so things should work just as before except that all the connection will be via https (except for images, etc if you using lighttp).
Assuming that everything is working, the last thing we do is set things up so that requests to http://yourserver.yourschool.edu/webwork2/ are automatically redirected to https://yourserver.yourschool.edu/webwork2/.
# gedit default
In the
<VirtualHost *:80>
section just above the line
ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
add the line
Redirect permanent /webwork2 https://yourserver.yourschool.edu/webwork2
where of course you should edit
yourserver.yourschool.edu appropriately.
Then save the file and quit.
Restart Apache
# apache2ctl graceful
and try connecting to http://yourserver.yourschool.edu/webwork2/. The real connection should be through https://yourserver.yourschool.edu/webwork2/.
Updating WeBWorK files
If you want to update a single WeBWorK file, e.g.
/opt/webwork/webwork2/lib/WeBWorK/Utils/FilterRecords.pm you can just do
$ cd /opt/webwork/webwork2/lib/WeBWorK/Utils
First do
$ svn status -u
This gives you the status of all files in the directory. For an explanation of the output see http://svnbook.red-bean.com/nightly/en/svn.ref.svn.c.status.html.
To update the file use
svn update FilterRecords.pm
If you want to update all files in a directory and in all its subdirectories, run the command
$ svn update
from the directory.
Where to go From Here
You should play around with
myTestCourse e.g. click on
Library Browser and browse the
Problem Library and also the
Rochester and
Union libraries.
Look at http://webhost.math.rochester.edu/webworkdocs/docs/courseadmin/usingwebwork
Read Course Administration for more information about creating courses.
Consult for other WeBWorK documentation for system administrators.
-- Main.ArnoldPizer - 15 Dec 2009


text:
I like the trend of making Father's Day cakes that look likes shirts and ties; it turns the cliche into something so much sweeter. Check these out:
Ok, so the sweater is a wee bit shiny, but you've got to admire the skill all that piping required. Plus, it's mostly fondant free!
For the more formal, pinstripe-wearing Dad, Jen C. found this one over at Jill's Sugar Collection:
See how those stripes pool into little dots at the bottom edge without breaking? That's talent. Kudos, Jill.
Laudine F. found this beautifully detailed number on De Leukste Taarten:
I'm not sure who the baker is exactly, though, since my Dutch is pretty rusty. (And by "rusty" I mean "non-existent".)
(UPDATE: Apparently y'all have non-rusty Dutch and the name of the baker is Lieselotte. Bedankt!)
And check out what Bakerella whipped up for Dad:
Those are mini cupcakes (with brownie centers) for the burgers, and sliced sugar cookies for the fries. Even better, Bakerella provides the templates to make the baskets & french fry holder for free on her site. (I'm sure you could modify that text for birthdays or other holidays.)
Oh, and a Happy Falker Satherhood to you all!