Automatic Installation Script Guide
WeBWorK Installation Script(s)
The github repository at https://github.com/openwebwork/ww_install contains a perl script "ww_install.pl", along with some supporting bash scripts, config files, and perl modules designed to work together install the open source online homework system WeBWorK.
The script has been updated to install WeBWorK 2.12 as of 3/2016.
It has been tested and supported on
- Debian 8
- Fedora 22, 23
- Ubuntu 15.10, 16.04 (LTS)
- CentOS 7
On these systems it did install WeBWorK.
To install WeBWorK:
1. Get the
wget --no-check-certificate https://raw.githubusercontent.com/openwebwork/ww_install/master/install_webwork.sh
or if you prefer
curl -ksSO https://raw.githubusercontent.com/openwebwork/ww_install/master/install_webwork.sh
2. As root (or with sudo) do
Note that if you use sudo, then you must be a sudoer with sufficient administrative rights (probably `ALL=(ALL) ALL`) for `install_webwork.sh` to work properly. If not, run this command as root.
For more control over the process you can clone this repository with
git clone https://github.com/openwebwork/ww_install.git
and then run ww_install.pl manually.
3. Answer the prompts as directed by the installer. Things to watch out for
- You will need to set the mysql root password. It should be different than your root/user password.
- Unless you have a good reason not to, use the standard installation directories.
- You can define a new WeBWorK admin user or use your current user. The WeBWorK admin user should not be root.
- You should use the usual WeBWorK data group unless you have a reason not to.
- Use https for your server root if you plan on setting up ssl. SSL is not set up automatically by the script.
- Do not change the relative location of the WeBWorK handler unless you have a reason to.
- You will probably need to contact your IT liaison to find out your smtp server (or make a guess).
- You will need to set the WeBWorK database password. It should be different than your mysql root password.
- Download from the usual repositories unless you have a reason not to.
- Use somewhere between 15-20 for each 1 GB of memory when setting MaxClients
4. The script will attempt to open a browser and start WeBWorK. You can login to the admin course with initial username and password 'admin'.
This script is the 'controller' that ties together the other scripts. It opens an install log, downloads this
repo and opens it in (typically)
/tmp. Then it installs any files needed to run
ww_install.pl and then runs
ww_install.pl exits, it attempts to open WeBWorK in the system's default web browser, copies
webwork_install.log to your top level webwork directory (e.g.
/opt/webwork) and then deletes the downloaded installation package.
The goal of
ww_install.pl is to install WeBWorK on any system with a properly set up distribution file in the
It is an interactive script based on the core perl module Term::UI, and is written with the goal of being cross-platform. It does use some linux built-ins, and work is needed to ensure that this script will work as well on unix machines. Again, contributions of work in this direction would be welcome.
This folder contains distribution files which
ww_install.pl uses to install WeBWorK on various systems. For example the file
distros/centos/7.pm is used to install WeBWorK on CentOS version 7. If you are interested in getting the installer working on your favorite distribution you would create the appropriate file in this folder. You can base your distro file off of
blankdistro.pm. In general you will need to set the following:
- The array of versions which you have tested the installer on.
- The list of packages which provide the binaries described by the hash keys
- The list of packages which provide the perl modules described by the hash keys. Use 'CPAN' if you intend to get the package from CPAN
apacheLayoutarray which defines where various folders and configuration files are for your apache setup.
- The command for updating package sources.
- The command for updating packages.
- The command for installing packages.
- The command for installing packages from CPAN.
- The command for checking and configuring services post install.
- You can add code in various "hooks" which will be run at various stages of the installation. This is an opportunity to perform any hacky fixes necessary for your distro.
extra/ subdirectory contains scripts which help with optional post install tasks. These are not currently hooked into the other scripts, so you'll need to run them separately. Currently contains
iptables_rules.sh: Sets up an iptables firewall which only allows network services necessary for running WeBWorK.
generate_ssl_cert.sh: Steps user through generating an ssl cert. Under construction.
install_chromatic.pl: Standalone script to compile
pg/lib/chromatic/color.cso the NAU library graph theory problems work. This functionality has been incorporated into
ww_install.pl, so it should not be necessary to run this script. However, if you find the NAU graph theory problems are complaining that
pg/lib/chromatic/colordoesn't exist, then you can run this script to compile it for you.
lib/subdirectory contains copies of any perl modules the script uses but which don't need to be installed on your system for webwork to run.
conf/subdirectory contains copies of config files or snippets of config files that this installation package will ask to modify.
Please report any problems on the issues page for the github repository.
Jason Aubrey <firstname.lastname@example.org>
I'd be happy to hear suggestions for improvement. Seriously, though. Send all your complaints to this guy.