Installation Manual for 2.3 on Debian 4.0

From WeBWorK
(Difference between revisions)
Jump to: navigation, search
Sam (Talk | contribs)
(New page: {{Historical}} These instructions cover the installation of the Debain Linux 4.0 operating system and %WW% 2.3 from scratch. They are more detailed (but offer fewer choices and often l...)
Newer edit →

Revision as of 19:20, 22 February 2008

This article has been retained as a historical document. It is not up-to-date and the formatting may be lacking. Use the information herein with caution.

These instructions cover the installation of the Debain Linux 4.0 operating system and %WW% 2.3 from scratch.

They are more detailed (but offer fewer choices and often less background information) than the general InstallationManualV2pt3 and are aimed at non unix experts. Readers may want to quickly scan InstallationManualV2pt3 to get an overview of the installation process and then carefully read and follow these instructions.

---++ Notation

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. =<Enter>=, =<Tab>=, =<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 Debian 4.0 rev0 Linux Operating System ---+++Installation DVD Obtain the installation DVD/CD set. Connect to [[1]] for information. For example you can use <nop>wxDownload Fast or <nop>BitTorrent to download ISO images of the installation DVD's and then burn your own installation DVD's. If you download ISO images, make sure that you verify the integrity of the downloaded files by comparing the MD5 checksums of the downloaded files with the MD5 checksums listed at www.debian.org. <nop>wxDownload Fast automatically calculates the MD5 checksums which is convenient. I have had good luck downloading from mirrors.kernel.org but your experience may differ. These instructions will assume you have the three installation DVD's but installing from a commercial DVD/CD set or a downloaded CD set or from the net should be essentially identical.

Place the first installation DVD in your DVD drive, turn the computer off and then back on, and boot 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. Note that with version 3.1 I had to physically turn the computer off and then turn it back on (not just reboot it) in order for the network card to be recognized by Debian but version 4.0 worked OK with just rebooting.

You will see a list of options.

  1. If you want hit =<F1>= to obtain help and see additional boot methods
  1. You can just hit =<Enter>= to accept the default install method except in the following situation
  1. If your network has DHCP enabled but you want to setup your server with a static IP address, then after the =boot:= prompt type =install netcfg/disable_dhcp<nop>=true= and then hit =<Enter>=
  1. A succession of pages follow, for each select the obvious option and hit =<Enter>=. For example my obvious options are =English=, =United States=, and =American English= 
  1. The system will than scan your DVD and load various components
  1. If your system has multiple network interfaces, you will be asked to select the one to be used during the installation (which will usually be a hard wired ethernet connection)
  1. Unless you entered the =netcfg/disable_dhcp<nop>=true= boot option above, the system will try to configure your network using DHCP. If you have DHCP, your network interface will be set up automatically.  If you don't have DHCP, automatic network configuration will fail quickly (or just hit =<Enter>= to =Cancel= if you are impatient). Then hit =<Enter>= to =Continue=

Manual network configuration. If your network interface was set up automatically by DHCP, you can skip the rest of this paragraph. Otherwise you will have to enter your machine's static ip address, etc. To do this

  1. Select =Configure network manually=
  1. Enter your computer's IP address and =Continue=
  1. The =netask= is probably OK as it but another possibility may be 255.255.0.0
  1. Enter the ip address of your gateway router. Debian makes a good guess at this, but your network may be set up differently.
  1. Next enter the ip address(es) of up to 3 nameservers  separated by spaces (at a minimum you have to enter the ip address one nameserver)
  1. Enter the name of your server and then
  1. Enter the domain name (e.g. mine is math.rochester.edu but yours is obviously different)
  1. This completes the static ip address setup

Next comes the =Partition disks= pages. You should be able to accept the defaults (unless you are dual booting operating systems, etc. but then you are not a novice user and you are on your own for that part)

  1. Select your time zone and wait for the clock to be configured
  1. Enter the password for the root user and confirm it. *Do not forget what you enter here*
  1. Choose to create a =normal user= and enter yourself as a user (with user name and password)
  1. Now the base installation will take place --- this may take a short time
  1. Choose to set up a network mirror. Select your country and a mirror. In the US I have found that mirrors.kernel.org works well
  1. You should be able to leave the proxy information blank
  1. I chose not to participate in the package usage survey

Next we come to software selection. Since it is much easier for a non unix expert to use a graphical user interface (GUI), we will install this. We will put off installing the necessary web server software until later.

  1. Under =Software selection= select =Desktop environment= and =Standard system= and then hit =Continue=
  1. Now sit back and relax while the installation takes place --- this may take awhile
  1. The last step is to install the boot loader. I have a non standard setup and for some reason I had trouble installing the Grub boot loader but Lilo worked fine. Almost certainly, Grub will work fine for you

---+++Continue Installation After this finishes the system will eject the DVD and ask you to reboot. Note that with version 3.1 I had to physically turn off the computer off and then turn it back on (not just reboot it) in order for the network card to be recognized but version 4.0 worked OK with just rebooting.

  1. Log into your regular account
  1. Accept any available updates (you will see a popup window). You will have to enter the =<root password>= but (if you keep the defaults checked) it will be saved for this session. Then click =install Updates=. Follow any instructions, e.g. if you install a new kernel, you may be told to reboot as soon as the installation is completed (to reboot, select =Desktop=, =Shut Down...= and then =Restart=)

---+++Debian Software Packages

Our next task is to install a number of Debian software packages.

  1. Select =Desktop=, =Administration= and then =Synaptic Package Manager=.   You will have to enter the =<root password>= if you rebooted above. The =Synaptic Package Manager= window will open
  1. First we make sure the package information is current. Select =Edit= and then =Add CD-ROM...=
  1. Place the second Debian DVD/CD in the DVD drive and it will be scanned for index files (the first one has already been scanned)
  1. Continue until you have scanned all of your remaining DVD/CD's and then select =<No>= to the =Scan another CD= question


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 =libapache-authnetldap-perl= and then just give the list of required packages.

  1. Select =Search= 
  1. Under =Look in:= select =Name=. The default =Description and Name= sometimes returns too many possibilities
  1. We are searching for =libapache-authnetldap-perl= so enter =ldap-perl= (or something similar) and click on =Search=
  1. This should result in 3 possibilities. Select and Mark for Installation (by double clicking or checking and then selecting =Mark for Installation=) =libapache-authnetldap-perl=. You will see a pop up window =Mark additional required changes?= and you should always click =Mark= to accept the requirements.
  1. Follow this basic procedure for all the packages listed below

Here is the list of Debian packages that need to be installed. See InstallationManualV2pt3 for a short explanation of what most of these packages do.

  1. =apache2=
  1. =apache2-mpm-prefork=
  1. =cvs=
  1. =dvipng=
  1. =libapache-authnetldap-perl=
  1. =libapache2-request-perl=
  1. =libdatetime-perl=
  1. =libdbd-mysql-perl=
  1. =libemail-address-perl=
  1. =libextutils-xsbuilder-perl=
  1. =libgd-gd2-perl=
  1. =libmail-sender-perl=
  1. =libossp-uuid-perl=
  1. =libstring-shellquote-perl=
  1. =libtimedate-perl=
  1. =libxml-parser-perl=
  1. =libxml-writer-perl=
  1. =mysql-server-5.0=
  1. =netpbm=
  1. =openssh-server=
  1. =preview-latex-style=
  1. =tetex-bin=
  1. =tetex-extra=

When I do this I see on the bottom of =Synaptic Package Manager= window =61 to install/upgrade= (note that I didn't install =libapache-authnetldap-perl= separately; if you did your number will differ). Now click =Apply= and =Apply= again to confirm the changes. You will be prompted to insert DVD's. After the packages are successfully installed, you can close the =Synaptic Package Manager= and remove your last DVD.


That completes the set up of your base Debian system.


---+++Test Browser and Keyboard

After your desktop reappears, click on =Applications=, =Internet=, =Icewease Web Browser= and you should be connected to the world. Goto [[2]] where you can view this document and, if you want, copy commands that you need (see below).

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 =Desktop=, =Preferences=, =Keyboard= and then increase the delay time interval and hit =Close=.

---++ Terminal Window Notation and Use

Before installing and configuring additional software, we need to talk about terminal windows.

To open a terminal window click =Applications=, =Accessories= and then select =Terminal= for a normal user or =Root Terminal= for root.

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. <verbatim>

  1. visudo

</verbatim>

and $ to indicate that the command is to be run as a normal user e.g. <verbatim> $ cp .bashrc .bashrc.bak1 </verbatim>

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 hit =<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 (with =paste= from the Edit dropdown list or =<Shift> <Ctrl> <V>=). However typing yourself using command completion is probably just as fast except if a command is long.

Finally perhaps a safer way to run commands as =root= is to use the =sudo= command <verbatim> $ sudo <command> password: <your password> </verbatim> After you enter the password the command is executed. For a certain period (maybe 5 minutes) you can execute additional =sudo= commands without reentering =<your password>=. A log of all =sudo= commands is kept (I don't know where). 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 =apache=). Note that in order to use sudo, you must be listed in the =sudoers= file. To do this open a =Root Terminal= and then <verbatim>

  1. visudo

</verbatim> A nano editing window will open up and you will be editing =/etc/sudoers.tmp= . At the end of this file add the line <verbatim> your_user_name ALL=(ALL) ALL </verbatim> where of course you replace =your_user_name= with your user name. Then hit =^X= to exit, =Y= to save changes and =<Enter>= to save changes to =/etc/sudoers.tmp=. Then =visudo= will automatically update the real =sudoers= file. It's a good practice to close the =Root Terminal= window so that you don't accidentally enter a command as root that you meant to run as a regular user.

For our next terminal window task open a (standard) terminal window and create a =downloads= directory where we will keep copies of downloaded software.

<verbatim> $ cd $ mkdir downloads </verbatim>


---++ Installing Perl Modules We now have to install one additional Perl module (=XML::Parser::EasyTree=) which is unfortunately 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: <verbatim> $ perl -MModule -e 'print "installed!\n"' </verbatim>

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

<verbatim> $ perl -MCPAN -e 'print "installed!\n"' </verbatim> yields <verbatim> installed! </verbatim> and <verbatim> $ perl -MXML::Parser::EasyTree -e 'print "installed!\n"' </verbatim> yields <verbatim> Can't locate XML/Parser/EasyTree.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.8.8 /usr/local/share/perl/5.8.8 ... </verbatim>


---+++ Installing Additional Perl Modules from CPAN

Be aware that in rare cases you might have to as root run

<verbatim> $ su <root password>

  1. unset LANG
  2. exit

$ </verbatim> 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. <verbatim> $ su <root password>

  1. perl -MCPAN -e shell

</verbatim> Since this is the first time you are using CPAN it will ask you =Are you ready for manual configuration?= Respond =no= and that should be it.

Next we add at least one mirror and reload the index. A list of mirrors can be found at [[3]]. 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. <verbatim> cpan> o conf urllist push ftp://mirrors.kernel.org/pub/CPAN cpan> reload index </verbatim>

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

<verbatim> cpan> install Bundle::CPAN </verbatim> 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 <verbatim> cpan> </verbatim> prompt enter

<verbatim> cpan> reload cpan cpan> o conf commit </verbatim>

Now install XML::Parser::EasyTree <verbatim> cpan> install XML::Parser::EasyTree </verbatim> and in case you are prompted accept all defaults by just hitting =<Enter>=. Note that if you have more than one module to install, you can just list them after =install= separated by spaces.

When you again see the <verbatim> cpan> </verbatim> prompt enter <verbatim> cpan> exit </verbatim>

---+++ 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 Debian 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 [[4]], 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

<verbatim> $ cd $ cd downloads $ tar -zvxf DateTime-0.36.tar.gz $ cd DateTime-0.36/


$ perl Makefile.PL $ make $ make test </verbatim> If =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.

=DateTime= requires the additional modules =version= , =Module::Build= , =Class::Singleton= , =DateTime::TimeZone= and =DateTime::Locale= . We could install these using CPAN

<verbatim>

  1. perl -MCPAN -e shell

cpan> install version Module::Build Class::Singleton DateTime::TimeZone DateTime::Locale cpan> exit

  1. exit

$ </verbatim>

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

<verbatim> $su <root password>

  1. make install
  2. exit

$ </verbatim> Finally you should definitely test that the module (e.g. =DateTime=) was installed sucessfully <verbatim> $ perl -MDateTime -e 'print "installed!\n"' </verbatim> If you see <verbatim> installed! </verbatim> you can celebrate.


---++ Apache 2 and mod_perl

First we have to enable a couple apache modules. Open a =Root terminal= or keep acting as =root= in a standard terminal and <verbatim>

  1. a2enmod apreq
  2. a2enmod info

</verbatim>

Next we make a copy of the apache configuration file for safekeeping. In the =Root terminal= <verbatim>

  1. cd /etc/apache2/
  2. cp apache2.conf apache2.conf.bak1

</verbatim>

Next we will edit the apache configuration file =apache2.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 =apache2.conf=. In the =Root terminal= <verbatim>

  1. cd /etc/apache2/
  2. gedit apache2.conf

</verbatim>

In the =gedit= edit window near the end of the file uncomment (i.e. remove the =#= 's from) the operational lines below. Leave the obvious comment lines (=# Allow server status reports ... domain to enable.= and =# Allow remote server configuration reports... domain to enable.=) commented.

The original lines are <verbatim>

  1. <IfModule mod_status.c>
   #
   # Allow server status reports generated by mod_status,
   # with the URL of http://servername/server-status
   # Change the ".example.com" to match your domain to enable.
   #
   #<Location /server-status>
   #    SetHandler server-status
   #    Order deny,allow
   #    Deny from all
   #    Allow from .example.com
   #</Location>
  1. </IfModule>
  1. <IfModule mod_info.c>
   #
   # Allow remote server configuration reports, with the URL of
   #  http://servername/server-info (requires that mod_info.c be loaded).
   # Change the ".example.com" to match your domain to enable.
   #
   #<Location /server-info>
   #    SetHandler server-info
   #    Order deny,allow
   #    Deny from all
   #    Allow from .example.com
   #</Location>
  1. </IfModule>

</verbatim>

Now in both places replace =Allow from .example.com= by =Allow from localhost=. If in addition you want to allow access to server information from e.g. your department domain, add new lines =Allow from .math.yourschool.edu= below the two =Allow from= lines where of course you should edit =.math.yourschool.edu= appropriately. The code (except for =yourschool=) should look like

<verbatim> <IfModule mod_status.c>

   #
   # Allow server status reports generated by mod_status,
   # with the URL of http://servername/server-status
   # Change the ".example.com" to match your domain to enable.
   #
   <Location /server-status>
       SetHandler server-status
       Order deny,allow
       Deny from all
       Allow from localhost
       Allow from .math.yourschool.edu
   </Location>

</IfModule>

<IfModule mod_info.c>

   #
   # Allow remote server configuration reports, with the URL of
   #  http://servername/server-info (requires that mod_info.c be loaded).
   # Change the ".example.com" to match your domain to enable.
   #
   <Location /server-info>
       SetHandler server-info
       Order deny,allow
       Deny from all
       Allow from localhost
       Allow from .math.yourschool.edu
   </Location>

</IfModule> </verbatim>

Then save the file and quit (=File=, =Save= and =File=, =Quit=.

Just to be sure you changed what you wanted do run <verbatim>

  1. diff apache2.conf apache2.conf.bak1
  2. exit

$ </verbatim> =diff= should report the changes you made and only those.

Now we have to set your server's fully qualified domain name.

  1. Select =Desktop=, =Administration=, =Networking=
  1. Click on =Hosts=
  1. Select the entry with IP Address 127.0.0.1 and click =Properties=
  1. Under Aliases first enter your server's fully qualified domain name, something like =your_server_name.department.school.edu=
  1. Next separated by a space or newline enter =localhost= 
  1. And finally, again separated by a space or newline, enter =your_server_name= (it's important that =localhost= comes first)
  1. Note that =localhost= and =your_server_name= are probably already listed in which case you only have to enter your server's fully qualified domain name as the first entry
  1. Then click =OK=

There should also be an entry with your server's IP address (if not you should add one)

  1. Select the entry with your server's IP address and click =Properties=
  1. Under Aliases you should see first your server's fully qualified domain name, something like =your_server_name.department.school.edu=
  1. And next, separated by a space or newline, =your_server_name=
  1. Add or edit these entries if they are not correct
  1. Then click =OK=
  1. And click =OK= again to close =Network settings=

You can check these settings by running the commands <verbatim>

  1. exit

exit $ hostname --fqdn </verbatim> and <verbatim> $ hostname </verbatim> The first respond with the fully qualified domain name and the second with just =your_server_name=.

Now restart Apache <verbatim> $su <root password>

  1. apache2ctl graceful
  2. exit

$ </verbatim> 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 <verbatim> Server Version: Apache/2.2.3 (Debian) mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.8.8 </verbatim> indicating that both =mod_apreq2= and =mod_perl= are installed.

---++ Checking <nop>MySQL

First check that <nop>MySQL is running by

<verbatim> $ mysql -u root </verbatim>

You should see <verbatim> Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 1 to server version: 5.0.26

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> </verbatim> Enter =exit= to exit <verbatim> mysql> exit Bye $ </verbatim>

---++ Reboot and Test

Now remove your DVD and reboot the system (=Desktop=, =Shut Down...=, =Restart=).

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 <nop>MySQL is running.

<verbatim> $ mysql -u root ... mysql> mysql> exit Bye $ </verbatim> Currently the <nop>MySQL password is empty so we didn't need a password. We will take care of that now.


---++ <nop>MySQL Security Issuses As initially set up, <nop>MySQL is an open system. The root accounts are not password protected. See e.g. [[5]] for information on this. We recommend giving passwords to the root accounts. There are two root accounts, one is =root@localhost= and the other is =root@host_name= where =host_name= is the name of your server. To find this name, do the following

<verbatim> $ mysql -u root mysql> SELECT Host, User, Password FROM mysql.user; </verbatim> You will see a table with three entries. For =localhost= you will see two Users, =root= and =debian-sys-maint=. The other listed Host (with only the =root= user) is the name of your server which we will denote by =host_name=. Now we will assign a password to these =root= accounts.

In the second command below, replace =host_name= with the name of the server host. In both commands replace =newpwd= with your choosen <nop>MySQL =root= password. As was said above, "Do not forget what you enter here". Also remember that this is the password for the <nop>MySQL =root= user, not the Debian linux system =root= user. Below we refer to this as =<mysql root password>=

<verbatim> mysql> UPDATE mysql.user SET password=PASSWORD('newpwd') WHERE host='localhost' and user='root'; mysql> UPDATE mysql.user SET password=PASSWORD('newpwd') WHERE host='host_name' and user='root'; mysql> FLUSH PRIVILEGES; </verbatim>

Now use your up arrow key to run the command <verbatim> mysql> SELECT Host, User, Password FROM mysql.user; </verbatim> and you should see that all three users now have passwords.

Then exit <nop>MySQL <verbatim> mysql> exit Bye $ </verbatim>

and test that all is well: <verbatim> $ mysql -u root -p Enter Password: <mysql root password> </verbatim> You should see <verbatim> Welcome to the MySQL monitor ... mysql> </verbatim> Enter <verbatim> mysql> SELECT Host, User, Password FROM mysql.user; </verbatim> and you should see encrypted passwords for all three accounts. Note that the way <nop>MySQL is set up, you can only gain access to the =localhost= account, not to the =host_name= account but setting a password for the =host_name= account is a safer thing to do in case the set up gets changed. Now exit <nop>MySQL <verbatim> mysql> exit Bye $ </verbatim> and congratulate yourself. You are now ready for the next and hopefully easy part, installing %WW%.

---++ Downloading the %WW% System Software and Problem Libraries We are finally at the point where we can start downloading and installing %WW%. We will use CVS to download %WW%. This is easy and it will also make it easy to update the system in the future. General instructions can be found in the WeBWorKCVSReadOnly topic but the following will get the job done. 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 <verbatim> $ cd $ cd downloads

$ cvs -d :pserver:anoncvs@cvs.webwork.rochester.edu:/webwork/cvs/system checkout -r rel-2-3-dev webwork2 pg $ cvs -d :pserver:anoncvs@cvs.webwork.rochester.edu:/webwork/cvs/rochester checkout rochester_problib $ cvs -d :pserver:anoncvs@cvs.webwork.rochester.edu:/webwork/cvs/union checkout union_problib $ cvs -d :pserver:anoncvs@cvs.webwork.rochester.edu:/webwork/cvs/asu checkout database_problems </verbatim> The first download gives you the latest released version with patches (don't be misled by the =dev= extension --- this is not a development version). The last download contains the %WW% National Problem Library. This now includes the Rochester and Union Libraries along with others but some people still find it convenient to use the Rochester and Union Libraries separately. There is quite a bit of overlap between these libraries but now you system is loaded with many thousands of %WW% problems (over 13,000 in the National Problem Library alone).


---++ Installing %WW% ---+++ Move the System into the Required Directories As =root= create a =webwork= directory under =/opt= and move directories there. <verbatim> $ su <root password>

  1. mkdir /opt/webwork
  2. mv webwork2 /opt/webwork/
  3. mv pg /opt/webwork/

</verbatim>

Now create the =courses= and =libraries= directories under =webwork= and copy and move content there. <verbatim>

  1. mkdir /opt/webwork/courses
  2. mkdir /opt/webwork/libraries
  3. mv database_problems/ /opt/webwork/libraries/
  4. mv rochester_problib/ /opt/webwork/libraries/
  5. mv union_problib/ /opt/webwork/libraries/
  6. cd /opt/webwork/webwork2/courses.dist
  7. cp *.lst /opt/webwork/courses/
  8. cp -r modelCourse/ /opt/webwork/courses/

</verbatim>

---+++ Setting Permissions

The PG installation directory and files should be owned by root and not writeable by other users: <verbatim>

  1. cd /opt/webwork/pg
  2. chown -R root:root .
  3. chmod -R u+rwX,go+rX .

</verbatim>

Most %WW% directories and files should also be owned by root and not writeable by other users: <verbatim>

  1. cd /opt/webwork/webwork2
  2. chown -R root:root .
  3. chmod -R u+rwX,go+rX .

</verbatim>

Certain data directories need to be writable by the web server. These are =DATA=, =courses=, =htdocs/tmp=, =logs=, and =tmp=. It is convenient to give %WW% 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 %WW% administrators and the web server.

  1. Select =Desktop=, =Administration= and then =Users and Groups=
  1. Select =Groups=
  1. Click =Add Group= 
  1. For =Group name= enter =wwdata=
  1. Under =Group Members= select yourself and click =Add=
  1. Under =Group Members= select =www-data= and click =Add=  (=www-data= is the Apache2 webserver)
  1. Click =OK=
  1. Click =OK= again

If there are other users who will also be administering %WW% files, now is a good time to add them. And remember to add them to the =wwdata= group as above.

You can check that this suceeded in a terminal window by entering

<verbatim>

  1. exit

$ id <your userid> </verbatim> and then you should see =wwdata= listed under groups. Also <verbatim> $ id www-data </verbatim> should show wwdata listed under groups. Now we make the %WW% 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. <verbatim> $ su <root password>

  1. cd /opt/webwork/webwork2/
  2. chgrp -R wwdata DATA ../courses htdocs/tmp logs tmp
  3. chmod -R g+w DATA ../courses htdocs logs tmp
  4. find DATA/ ../courses/ htdocs/ logs/ tmp/ -type d -a ! -name CVS -exec chmod g+s {} \;
  5. exit

$ </verbatim>

---++ Configuring the Shell

To make working with %WW% easier, there are a couple of changes you can make to your shell environment.

Add the %WW% =bin= directory to your path. This will allow you to run %WW% command-line utilities without typing the full path to the utility. Goto your home directory and backup your =.bashrc= file

<verbatim> $ cd $ cp .bashrc .bashrc.bak1 </verbatim>

Now edit =.bashrc=

<verbatim> $ gedit .bashrc </verbatim>

After the last line add the two lines: <verbatim> export PATH=$PATH:/opt/webwork/webwork2/bin export WEBWORK_ROOT=/opt/webwork/webwork2 </verbatim> 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 <verbatim> $ echo $PATH $ echo $WEBWORK_ROOT </verbatim>

---++ Checking Module Dependancies


%WW% 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.

<verbatim> $ check_modules.pl apache2 </verbatim>

Scroll up and look through the listing. It should find everything except =PHP::Serialization= which is only required if you plan to use %WW% with Moodle and =tth= which is a deprecated display mode. If something is missing (flagged by =**=), look back through these instructions to find where it should have been installed and install it. ---++ Configuring %WW%

---+++ 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/= . Since these are owned by =root= <verbatim> $ su <root password>

  1. cd /opt/webwork/webwork2/conf
  2. cp global.conf.dist global.conf
  3. cp database.conf.dist database.conf

</verbatim>

---+++ Global Configuration

Most %WW% configuration is done in the file =/opt/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 %WW% to work with your system. The rest of the file consists of customization options. Now edit =global.conf=

<verbatim>

  1. cd /opt/webwork/webwork2/conf
  2. gedit global.conf

</verbatim>

  1.Search for =$externalPrograms{tar}      =<nop> "/usr/bin/tar";= and replace this by 
=$externalPrograms{tar} =<nop> "/bin/tar";= 1.Now directly below this add the new line
=$externalPrograms{gzip} =<nop> "/bin/gzip";=
or edit it appropriately if it's already there.

%WW% uses the <nop>DateTime module. <nop>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 <nop>DateTime go to [[6]] . 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 replace =$siteDefaults{timezone} =<nop> "";= by =$siteDefaults{timezone} =<nop> "America/New_York";=

  1.Search for =$siteDefaults{timezone} =<nop> "";= and enter your local timezone.

At this point =TtH= is a deprecated display mode which we didn't install so we have to remove it from the listof possible display modes.

  1. Search for =formattedText= and comment out the line =   "formattedText", # format math expressions using <nop>TtH=

so it becomes <verbatim>

  1. "formattedText", # format math expressions using TtH

</verbatim>

We need to set a password that %WW% uses when it communicates with the <nop>MySQL database.

  1.Search for =$database_password =<nop> "";=    and replace this by 
=$database_password =<nop> "database_password";=

where of course you should replace 'database_password' with your own password. Remember this password as we will need it below.

%WW% 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, %WW% 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, %WW% 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).

  1. Edit the lines =$mail{smtpServer}            =<nop> 'mail.yourschool.edu';= and 
  1. =$mail{smtpSender}            =<nop> 'webwork@yourserver.yourschool.edu';= 

entering the appropiate information

If you want %WW% questionnaires or similar things from different courses to be mailed to a central person or persons (e.g. the %WW% administrator), edit the lines <verbatim> $mail{allowedRecipients} = [

  #'prof1@yourserver.yourdomain.edu',
  #'prof2@yourserver.yourdomain.edu',

]; </verbatim> appropriately. In order to have professors from individual courses receive such email, this should be set in course.conf to the addresses of professors of each course.

Then save the file and Quit.


Now become a regular user again

<verbatim>

  1. exit

$ </verbatim>

%WW% 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): <verbatim> $ 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 $ </verbatim>

where as we said replace =database_password= with the password you set when editing =global.conf= above.

%WW% 2.3.0 introduces an automatic database upgrade system. Rather than manually issuing SQL commands to make changes to the database, or using ad-hoc scripts like wwdb_addgw, there is a single script called =wwdb_upgrade= that applies any necessary updates. It should be run when creating a new database, and any time you upgrade %WW%.

$ /opt/webwork/webwork2/bin/wwdb_upgrade -v

You will get the error message <verbatim> An error occured while running the course upgrade code for version 2 on course modelCourse: ... Ignore this error and go on to the next course? [y/N] </verbatim> You should enter =Y= to ignore the error. This error occurs because =wwdb_upgrade= isn't smart enough to realize =<nop>modelCourse= isn't a real course as we explain below.


---+++ jsMath Settings

Version 2.0 of jsMath introduced a new fallback method for when the <nop>TeX fonts are not available on the student's computer. This uses images of the individual <nop>TeX characters in place of the <nop>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 <verbatim> $ su <root password>

  1. cd /opt/webwork/webwork2/htdocs/jsMath
  2. tar vfxz jsMath-fonts.tar.gz

</verbatim>

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.


---++ Configuring Apache %WW% 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 =webwork.apache2-config=: <verbatim>

  1. cd /opt/webwork/webwork2/conf
  2. cp webwork.apache2-config.dist webwork.apache2-config

</verbatim> and now link it into your Apache configuration process <verbatim>

  1. cd /etc/apache2/conf.d
  2. ln -s /opt/webwork/webwork2/conf/webwork.apache2-config webwork.conf

</verbatim>

Then restart Apache <verbatim>

  1. apache2ctl graceful

</verbatim>

If this doesn't work and you see the error <verbatim> Syntax error on line 29 of /opt/webwork/webwork2/conf/webwork.apache2-config: $parms->add_config() has failed: Option FollowSymLinks not allowed here at /usr/lib/perl5/Apache2/PerlSections.pm line 203.\n </verbatim> we have to do some more work. If you don't get this error, you can skip this section and go on to Test your configuration. At the time these instructions are being written Debian has packaged mod_perl version 2.0.2 which has a small bug which seems to be fixed in version 2.0.3. However we have a pretty easy work around for version 2.0.2. Edit =webwork.apache2-config= as follows:

<verbatim>

  1. cd /opt/webwork/webwork2/conf
  2. gedit webwork.apache2-config

</verbatim>

Replace the end of the file (starting with =# Provide access to system-wide resources.=) with the section below. What we are doing is commenting out the two =Directory= blocks within the main =Perl= block, moving them below (i.e. outside) the main =Perl= block and then replacing perl variables =$webwork_htdocs_dir= and =$webwork_courses_dir= with the actual directories.


<verbatim>

  1. Provide access to system-wide resources.

push @Alias, [ $webwork_htdocs_url => $webwork_htdocs_dir ];

  1. $Directory{$webwork_htdocs_dir} = {
  2. Order => "allow,deny",
  3. Allow => [qw/from all/],
  4. Options => "FollowSymLinks",
  5. AllowOverride => "None",
  6. };
  1. Provide access to course-specific resources.

push @AliasMatch, [ "$webwork_courses_url/([^/]*)/(.*)", "$webwork_courses_dir/\$1/html/\$2" ];

  1. $Directory{"$webwork_courses_dir/*/html"} = {
  2. Order => "allow,deny",
  3. Allow => [qw/from all/],
  4. Options => "FollowSymLinks",
  5. AllowOverride => "None",
  6. };
  1. If WeBWorK is on the root, exempt the static directories from being handled
  2. by Apache::WeBWorK.

if ($webwork_url eq "") {

  $Location{$webwork_courses_url} = { SetHandler => "None" };
  $Location{$webwork_htdocs_url} = { SetHandler => "None" };

}

</Perl>

<Directory /opt/webwork/webwork2/htdocs>

   Allow from all
   AllowOverride None
   Options FollowSymLinks
   Order allow,deny

</Directory>

<Directory /opt/webwork/courses/*/html>

   Allow from all
   AllowOverride None
   Options FollowSymLinks
   Order allow,deny

</Directory> </verbatim>


Then save the file and Quit.

Restart Apache <verbatim>

  1. apache2ctl graceful

</verbatim>

and all should be well.

<verbatim>

  1. exit

$ </verbatim>

---++ Test your configuration

  1.Test the =/webwork2= location by visiting =http://yourserver.yourschool.edu/webwork2=. You should see the %WW% home page with no courses listed.  Actually the directory =/opt/webwork/courses/= does contain the =modelCourse= but the =modelCourse= is 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_directory= and so the =modelCourse= is not visible.
  1.Test the =/webwork2_files= location by visiting =http://yourserver.yourschool.edu/webwork2_files=. You should see the "%WW% Placeholder Page".
  1.You cannot test the =/webwork2_course_files= location 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). 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.

<verbatim>

  1. 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 </verbatim>

If something is wrong and you fix it, you will have to restart Apache for the changes to take effect <verbatim> $ su <root password>

  1. apache2ctl graceful
  2. exit

$ </verbatim> ---

---++ Create the admin Course

The CourseAdministrationManual gives information about creating courses. Here we will give explicit instructions for doing this.

<verbatim> $ su <root password>

  1. newgrp wwdata
  2. umask 2
  3. cd /opt/webwork/courses
  4. /opt/webwork/webwork2/bin/addcourse admin --db-layout=sql_single --users=adminClasslist.lst --professors=admin
  5. exit
  6. exit

$ </verbatim>

Now goto =http://yourserver.yourschool.edu/webwork2= and should see the %WW% 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 to 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. %WW% 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 %WW% administrator. To do this (assuming you are logged in as =admin= to the =admin= course at =http://yourserver.yourschool.edu/webwork2/admin= )

  1. Click on =Classlist Editor= in the left panel
  1. Check =Add 1 student(s)= and click =Take Action!=
  1. Enter the appropiate information (you can leave the last three items blank) and click =Add Students=
  1. Click on =Classlist Editor= in the left panel again
  1. When you enter a new student, by default their =Student ID= is used as their password. We'll change this now.
  1. Select yourself with a check mark and then check =Give new password to Selected users= or 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!=
  1. Enter the password, check =Save changes= and then click =Take Action!=
  1. Finally give yourself =professor= privilges by selecting yourself with a check mark, checking =Edit Selected users= and 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)
  1. Now at the far right change =Permission Level= from 0 (an ordinary student) to 10 (an esteemed professor)
  1. Check =Save changes= and then click =Take Action!=

At some point you will probably want to hide the =admin= course so that it is not listed on the %WW% 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 %WW% 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 %WW% 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 %WW% home page =http://yourserver.yourschool.edu/webwork2= . Let's hide the =admin= course.

<verbatim> $ cd $ gedit hide_directory </verbatim>

Now you don't really have to put any verbiage in the file but I suggest you put: <verbatim> Place a file named "hide_directory" in a course or other 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. </verbatim>

Save the file and quit. Now copy the file to the =admin= course.

<verbatim> $ sudo cp hide_directory /opt/webwork/courses/admin password:<your password> </verbatim>

Now goto =http://yourserver.yourschool.edu/webwork2= and no course will be listed.

---++ Starting and Stoping Apache, <nop>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 ocassions you may need to restart =<nop>MySQL=. ---+++ Starting and Stoping Apache You have to run these commands as =root=.

To start or restart (i.e. stop and then start) the =apache2= webserver run the command <verbatim> $ sudo apache2ctl graceful password:<your password> </verbatim> To stop the =apache= webserver run the command <verbatim> $ sudo apache2ctl stop password:<your password> </verbatim>

You can also start or stop apache2 by using the GUI interface.

  1. Select =Desktop=, =Administration= and then =Services=
  1. If  =apache2= is running, uncheck its check box and click =OK= to stop it
  1. If  =apache2= is stopped, check its check box and click =OK= to start it

Note that I found using =apache2ctl= a more robust way to start and stop =apache2=.

---+++ Starting and Stoping <nop>MySQL You have to run these commands as =root=.

To start the =<nop>MySQL= server run the command <verbatim> $ sudo /etc/init.d/mysql start root's password:<root password> </verbatim> To stop the =<nop>MySQL= server run the command <verbatim> $ sudo /etc/init.d/mysql stop root's password:<root password> </verbatim> To restart the =<nop>MySQL= server run the command <verbatim> $ sudo /etc/init.d/mysql restart root's password:<root password> </verbatim>

You can also start or stop <nop>MySQL by using the GUI interface.

  1. Select =Desktop=, =Administration= and then =Services=
  1. If  =mysql= is running, uncheck its check box and click =OK= to stop it
  1. If  =mysql= is stopped, check its check box and click =OK= to start it

---+++ 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

<verbatim> $ sudo /etc/init.d/gdm stop password:<password> </verbatim>


If you stopped =GNOME= and want to restart it run the following in a standard terminal window <verbatim> $ sudo /etc/init.d/gdm start password:<password> </verbatim>

---++Install the %WW% Problem Libraries Before we create a real course we will install the %WW% Problem Libraries.

---+++Install the National Problem Library The =National Problem Library= consists of both %WW% problems and methods for searching and selecting problems. Also it contains as sub libraries many of the other standard libraries. Normally this library is referred to as the =ProblemLibrary= but the downloaded CVS directory for it is named =database_problems=. So the first thing we do is to link =ProblemLibrary= to =database_problems=.

<verbatim> $ cd /opt/webwork/libraries/ $ sudo ln -s database_problems ProblemLibrary password:<password> </verbatim>


Next we have to edit =global.conf=.

<verbatim> $ cd /opt/webwork/webwork2/conf $ su Password: <root password>

  1. gedit global.conf

</verbatim>

  1.Search for =problemLibrary= and replace =$problemLibrary{root}        =<nop> "";= by 
=$problemLibrary{root} =<nop> "/opt/webwork/libraries/ProblemLibrary";=

Then save the file and quit. And return to a regular user <verbatim>

  1. exit

$ </verbatim>

We now create a database, called =ProblemLibrary=, for for the Problem Library. To do this do the following: <verbatim> $ mysql -u root -p mysql Enter password: <mysql root password> mysql> CREATE DATABASE ProblemLibrary; mysql> GRANT SELECT ON ProblemLibrary.* TO webworkWrite@localhost; mysql> exit Bye $ </verbatim>

Run the installation script making sure you are in the =/opt/webwork/libraries/ProblemLibrary= directory. This directory contains the files =loadDB2= and =create_tables2.sql=.

<verbatim> $ cd /opt/webwork/libraries/ProblemLibrary $ ./loadDB2 <mysql root password> </verbatim>

This has to convert a lot of data 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 loadDB.pl.

---+++Set up the Rochester and Union Libraries

First we need to edit =global.conf= one last time

<verbatim> $ cd /opt/webwork/webwork2/conf $ su Password: <root password>

  1. gedit global.conf

</verbatim>

  1.Search for =courseFiles{problibs}= and scroll down several lines to the line 
=# rochesterLibrary =<nop>> "Rochester",= 1.Uncomment this line (i.e. remove the =#=) so it becomes

         =rochesterLibrary =<nop>> "Rochester",=

  1.Directly below this line add the line 

         =unionLibrary =<nop>> "Union",=

  1.Search for =macrosPath= and scroll down several lines to the line 
=$pg{directories}{macros},= 1.After this line add the two lines:
='/opt/webwork/libraries/union_problib/macros',=
='/opt/webwork/libraries/union_problib/parserOrientation',=

Then save the file and quit.

Since we have edited =global.conf= a lot and this is a very critical file, it would be a good idea to run

<verbatim> $ diff global.conf global.conf.dist </verbatim> and check that you haven't made any mistakes (e.g. by introducing an inadvertant line break, etc).

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.

<verbatim> $ cd /opt/webwork/courses/modelCourse/templates/ $ sudo ln -s /opt/webwork/libraries/union_problib/ unionLibrary Password:<your password> $ sudo ln -s /opt/webwork/libraries/rochester_problib/ rochesterLibrary </verbatim>

---++Create Your First Actual Course

Now log into the =admin= course ( =http://yourserver.yourschool.edu/webwork2/admin= ) as yourself or =admin= and

  1.click on =Add Course=
  1.For =Course ID= enter =myTestCourse=
  1.For =Course Title= enter =My Test Course=
  1.Enter your institution
  1.Leave =Add %WW% administrators to new course= checked
  1.Add an additional instructor if you wish
  1.Copy templates from: =modelCourse= (the default action)
  1.Select sql_single for the  database layout.
  1.Click on =Add Course=
  1.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.

---++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 [[7]]

Read the CourseAdministrationManual for more information about creating courses.


Consult the WeBWorKDocs topic for other %WW% documentation.


---

-- Main.ArnoldPizer - 21 June 2007 Initial version based on Sam Hathaway's InstallationManualV2pt3

follow us