Projects: Global Lab : GL local development site
This page last changed on Nov 08, 2007 by pburney.
The code was developed on Mac OS X and is currently running on a Linux server. If you plan to develop on a Windows machine, you may need to make some adjustments to the code related to file paths as well as customize the setup of the tools for your software versions.
Apache should be version 2 or greater.
MySQL should be version 4.1 or greater.
PHP should be version 5 or greater.
Grab the database exports from here:
Login to your local MySQL server as the root user.
Create the Global Lab database:
Grant access to a global lab user.
Switch to using that database
Import data from an exported file.
Create a directory to house various web files
Create a directory to store log files and make that directory writable by the webserver
Change to the web directory
Check out a fresh copy of the code from the subversion repository
Copy the distributed configuration file and add in your own development database passwords, server paths, etc.
The key changes to make are in these items:
Now ensure that classes will have permission to upload photos:
For local development, it's easiest to use a name like globallab.concord.local. To get your machine to understand that, you'll need to edit the hosts file.
On Macs and Linux, the file is at /etc/hosts.
On Windows, the file is at \WINDOWS\system32\drivers\etc\hosts
You'll need to add a line like this to the file:
Edit the httpd.conf file and add the following lines to it:
Now the site should be set up and working. If the site isn't running, check the error log. A nice way to do this is to use the tail command with the -f parameter in a terminal window. It will update with any changes to the file:
Do your development of the site now. When you are done and everything is working locally...
You can commit your changes when you are done, using something like this syntax:
If you omit the files to be committed, all files in that directory downward will be committed
Once you're sure your changes are good and not breaking anything, you can update the development server:
Then check the development server to see if everything is working.
If it is, tell project members to look at the work you've done. After the work is approved, Paul Burney will move the changes to the PRODUCTION server
|Document generated by Confluence on Jan 27, 2014 16:42|