AMO: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 106: Line 106:


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.
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.
No error messages will be displayed by default.  You can change that via .htaccess or ini_set - you must change display_errors to 1 and set error_reporting.


== Other Documents ==
== Other Documents ==

Revision as of 01:23, 16 April 2005

About

UMO (Updates Mozilla Org) provides web-based services like addons.mozilla.org providing a resource for finding and installing Extensions and Themes for Firefox and Thunderbird, as well as the Plugin Finder and Application Update services.

Project Status

There is a commit freeze for v1.0. A full security audit is in progress. Some features will be disabled until that is completed. We will provide a more accurate timeline as it becomes available.

When is X going to happen?

Until we have a clear picture of what we have and where we are going, we won't have a timeline. Right now the goal is to get an assessment completed by 2005-03-01 which will help drive our development efforts moving forward.

Meetings

Contact Information

General

  • Mailing list: umo-admins@mozilla.org
  • IRC: #umo on irc.mozilla.org

Leads

  • Module Owner: Scott Kveton, kveton on irc.m.o
  • Mozilla Foundation Lead: Christopher Beard, cbeard on irc.m.o, cbeard at mozilla dot org

Collaborators

  • Mike Morgan, morgamic on irc.m.o, Reviewer
  • Alan Starr aka alanjstr
  • Giorgio Maone, maoztetung on irc.m.o., g.maone at informaction,com, Reviewer
  • Chris Thomas, CTho on irc.m.o, cst at andrew,cmu,edu, Reviewer
  • Colin Ogilvie, Colin on irc.m.o, colin.ogilvie AT gmail DOT com
  • Mike Connor, mconnor on irc.m.o, Reviewer
  • Alex Sirota, iosart on irc.m.o., alex at elbrus,com
  • Dave Miller, justdave on irc.m.o (production system administrator)
  • Barry Chen, chenb on irc.m.o
  • Johnny Stenback, [[User::jst|jst]] on irc, Plugin Finder Service.

Requirements

See a complete list of project requirements.


Infrastructure

In looking at the future, we need to identify what it's going to take to handle the UMO service during peak loads. The community will not judge us on how sexy UMO is or the tools built around it. We believe the community and pundits will be most critical of UMO if it fails to perform during peak usage. If a new security update is released and UMO melts down, that will reflect poorly on the use of Firefox but also the Mozilla Foundation as a whole.

The existing infrastructure will not scale to handle peak loads at this time. Peak loads will occur when new and popular extensions come out and most notably when security updates are released. We need to build a scalable, reliable and secure infrastructure to handle the delivery of the UMO service to end users.

Corey Shields will be tasked with coming up with a plan for this and presenting it to the Mozilla Foundation system administrators. The OSL would be willing to completely manage this service up to the application layer (including upgrades, etc) for the MoFo.

Roadmap

v1.0

We are only going to be doing security and performance fixes to this release. This will tie into the security audit which will identify any changes that need to happen before we turn UMO on with the v1.0 codebase.

v2.0

The overall opinion is we should rewrite from scratch to take advantage of frameworks/tools to improve scalability and extensibility. See the complete v2.0 plan.

Developer's Guide

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.

Anonymous CVS Access

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 checkout -d mozilla-update mozilla/webtools/update

Staging Environment

Dev Environment

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.

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.

No error messages will be displayed by default. You can change that via .htaccess or ini_set - you must change display_errors to 1 and set error_reporting.

Other Documents

Retrieved from "https://wiki.mozilla.org/index.php?title=AMO&oldid=5374"