TeamProjects Page History

Team Projects

Most undergraduates and MSc students undertake a team project for which certain shared facilities are required. For each module, students are organised by the module leader into teams of about 10 people. Each team is assigned a moderator, normally a member of staff.

Mailing list

A semi-private mailing list will be created. Members of the team (and possibly the team moderator) will have unrestricted access to the list. Non-members may also post to the list, but will be required to confirm all postings in an attempt to reduce the number of unwanted messages. The postings will be archived for the duration of the project. When posting, please take care to use the list address rather than that of the list maintainer which ends in -request. Messages to the list maintainer that appear to be destined for the list will not be forwarded. You can find out which lists you are subscribed to and hence which team you are a member of by signing on to the University's email list management service with your normal campus ID.

Gitlab repository

A local gitlab version control server holds a repository for each team. Please remember to log in with your campus ID using the Kerberos button.

Web space

Web space for each team has been created and linked to your team's gitlab repository. This web space is not directly updatable other than by checking the content in to the subfolder website in your repository. Any content checked in to here is automatically uploaded to your team web space with a delay of up to 10 minutes. The web server that serves these pages has been configured to use PHP so long as you use the .php filename suffix.

A typical URL for the project will be as below (with appropriate substitutions for Year (e.g. 2018-19), Module and Team.:-

This repository can be updated using TortoiseGIT or any other git client of your choice.


If requested by your module leader, a database will have been created for each team. The username and password for this will be sent to the team members by email, making use of the team mailing list. Please remember that this username and password will probably need to be embedded in scripts or web pages so should not be set to be the same as your campus password.

Direct SQL access to the database is restricted to on-campus hosts - see Databases for details of how a secure tunnel may be opened for remote database administration.

Last edited by Chris Ritson