Steven - 2012-08-21

Football Website

Abstract

This site was developed for a small, local football club. The requirement was to hold fixtures, results and match reports and to deliver news and events.

Over time, facilities for a second team were asked for, a moderated guestbook area for public comments was added, player profiles were desired and photographs could be uploaded & stored on the database.

Technology & evolution

Written in php with a postgresql backend, the site was first created back in 2005 to hold basic news and match information for a single team.

After three years service the front end was redeveloped to use JSON as per the Prototype framework but the database barely changed at all.

Set-up

What is available in the trunk in Subversion is a fully working copy of the system. A working example system may be set up using the following steps.

Prerequisites:

* Web Server
* php v5
* postgresql v8
* Two postgresql users: 
    + user: steven         password: steven
    + user: steven_update  password: steven_update

Steps

  1. Check out the code. Check out trunk to a directory called footballsite.
  2. Unzip the .gz files in the footballsite/schema directory.
  3. Create the database
    As the postgres superuser:
    CREATE DATABASE footballsite;
    ALTER DATABASE footballsite OWNER TO steven;
  4. Read in the database structure
    As user steven:
    cd footballsite/schema
    psql < footballsite_structure.sql
  5. Read in the example data
    As user steven:
    cd footballsite/schema
    psql < footballsite_data.sql

URLs

Interface URL
Administration http://localhost/footballsite/www/maint
Public http://localhost/footballsite/www/site

The site Maintenance Usernames and md5-encrypted passwords are held in the database. Again the user is steven and the password is also steven.

Naturally it is recommended that all the user names above be tailored to your utmost desire...

Disclaimer

All code is supplied as-is and no warranty is given or implied, not even for fitness of purpose. Use at your own risk: No liability whatsoever will be accepted for any losses - financial, human or otherwise - to any persons and/or organisations.

To the best of my knowledge, all third party components (some images, the HTML editor, the CAPTCHA code and other parts) were, at the time of coding and are still at this point in time, free to use, even for commercial purposes. Again these parts are used at your own risk: The onus is on YOU to perform due diligence on these parts. I will not accept any liability for losses, damages, deaths or anything else.

 

Last edit: Steven 2012-08-26