Update:Archive/2.0/Developers Guide

Website Developer's Guide

• Development Tools
• Best practices and coding standards
• Supported Server Configuration
• Reusable Code
• Review Process

We grab the update and plugin files as well as the database every 4 hours from the production servers. In addition, we also update the /data/update-dev and /data/update-staging via cvs every 4 hours as well.

If you like to and have the skills, you can help UMO by writing patches for the bugs that are in the system. For all known bugs in UMO, please go to the Bug List. To get access to the UMO code, read the Anonymous CVS Access intructions below.

In order to get your patch to be applied in the CVS, join the IRC channel #umo on irc.mozilla.org.

Anonymous CVS Access

• http://www.mozilla.org/cvs.html

setenv CVSROOT :pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot  
cvs login
(password is "anonymous")

NOTE: you want to do this from your public_html directory:

cvs co -rMOZILLA_UPDATE_1_0_BRANCH -d . mozilla/webtools/update

Dev Environment

• https://update-dev.mozilla.org:8080/
• /data/update-dev/

Sandbox Environment

Each developer can use a sandbox environment on chameleon.mozilla.org hosted in their public_html directory. If you would like access to this environment talk with kveton in #umo on irc.mozilla.org. This will allow you to do testing of patches and do custom development in your own sandbox and not affect the production development or staging environments.

• http://update-staging.mozilla.org/~username/
• /home/username/public_html

The latest dump of the UMO database is in /data/db on chameleon. To use it just grab it and put it in your home directory and run:

• cp mozilla-update.sql .
• mysql -u username -p --database username < mozilla-update.sql

You can edit your database via phpmyadmin if you go to https://update-staging.mozilla.org/db/ using your sandbox username/password. You will be asked to enter your password twice as the first one is an htaccess password to protect the phpmyadmin tool behind it.

All error messages will be displayed by default. Unless you are trying to eliminate all notices, you may want to change this to E_WARNING in order to actually get by. You can change that via .htaccess or ini_set. To do this, you can set the following in your config.php:

ini_set('error_reporting', E_WARNING); 
ini_set('display_errors', true);